GitLab Runner: Step 3: Connect your runner

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!

Head back to your Stackhero dashboard, open your GitLab Runner service configuration, and enter the following details:

• Your GitLab URL: Use https://gitlab.com for GitLab.com, or the URL of your self-managed GitLab instance (for example, if you are running GitLab on Stackhero, this might be https://git.your-company.com).
• The runner authentication token (glrt-...) you obtained in Step 2.
• The number of concurrent jobs you would like to allow.

Once you save your configuration, your runner will automatically connect to GitLab and appear as online on the Runners page where you created it.