GitLab Runner: Step 3: Connect your runner

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!

Return to your Stackhero dashboard, open your GitLab Runner service configuration, and enter the following information:

• Your GitLab URL: Use https://gitlab.com for GitLab.com, or the URL of your self-hosted GitLab instance (for example, if you are running GitLab on Stackhero, this might be https://git.your-company.com).
• The runner authentication token (glrt-...) obtained in Step 2.
• The number of concurrent jobs you wish 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.