GitLab Runner: Step 4: Run your first pipeline

This documentation is part of the Getting started guide. View the full guide here: Connect your Stackhero GitLab Runner to GitLab.com or a self-managed GitLab and run your first pipeline.

👋 Welcome to the Stackhero documentation!

Stackhero gives you an easy-to-use GitLab Runner cloud solution designed to handle your GitLab CI/CD jobs efficiently. Here is what you can look forward to:

• Unlimited CI/CD minutes: there is no per-minute billing, so your pipelines can run whenever you need them.
• Multiple concurrent jobs: run several jobs at the same time to speed up your entire pipeline.
• The Docker executor with Docker-in-Docker support: streamline building and pushing your container images.
• Compatible with GitLab.com as well as any self-managed GitLab instance.
• A private, dedicated VM powered by fast NVMe/SSD disks for consistent, reliable builds.
• Available in both 🇪🇺 Europe and 🇺🇸 USA regions.

Save time: you can connect your first GitLab Runner and start running pipelines in just a few minutes!

To get started, add a .gitlab-ci.yml file at the root of your repository:

stages:
  - build
  - test

build:
  stage: build
  image: node:22
  script:
    - npm ci
    - npm run build

test:
  stage: test
  image: node:22
  script:
    - npm test

Commit and push your changes. GitLab will start a pipeline, and your Stackhero runner will execute the jobs. If you added tags when creating the runner, you may want to target them in your jobs like this:

build:
  stage: build
  tags:
    - stackhero
  image: node:22
  script:
    - npm ci
    - npm run build

That is it. Your pipelines are now running on your own dedicated runner, with unlimited build minutes.