GitLab Runner: Step 2: Create a runner in GitLab

This documentation is part of the Getting started guide. You can view the complete guide here: Connect your Stackhero GitLab Runner to GitLab.com or a self-hosted GitLab and run your first pipeline.

👋 Welcome to the Stackhero documentation!

Stackhero offers you an easy-to-use GitLab Runner cloud solution, designed to efficiently run your GitLab CI/CD jobs. Here’s what you can benefit from:

• Unlimited CI/CD minutes: there’s no per-minute billing, so your pipelines can run whenever you need them.
• Concurrent jobs: run multiple jobs in parallel to speed up your entire pipeline.
• The Docker executor with Docker-in-Docker support: simplify 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 reliable, consistent builds.
• Available in both 🇪🇺 Europe and 🇺🇸 USA regions.

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

Your runner connects to GitLab using a runner authentication token. You will generate this token in GitLab, where you will also define the runner's scope:

• Project runner: Open your project, then go to Settings > CI/CD > Runners > New project runner.
• Group runner: Open your group, then go to Settings > CI/CD > Runners > New group runner.
• Instance runner (for self-hosted GitLab only): Go to the Admin area > CI/CD > Runners > New instance runner.

When creating the runner, you can:

• Add tags (such as docker or stackhero) to help you target this runner from your jobs.
• Allow it to run untagged jobs if you want it to pick up all jobs.

GitLab will provide a runner authentication token starting with glrt-. Make sure to keep this token secure, as it is what your runner uses to authenticate.

The old registration token method is deprecated. Please use the runner authentication token (glrt-...) created alongside the runner, as described above.