GitLab Runner: Step 2: Create a runner in GitLab

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!

Your runner connects to GitLab using a runner authentication token. You will generate this token in GitLab, where you also decide 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-managed GitLab only): Go to the Admin area > CI/CD > Runners > New instance runner.

When you create the runner, you can:

• Add tags (like 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 every job.

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

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