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, Stackhero for GitLab, or your own GitLab server and launch your first pipeline in just a few minutes.

👋 Welcome to the Stackhero documentation!

Stackhero offers a straightforward GitLab Runner cloud solution that makes running your GitLab CI/CD jobs efficient and hassle-free. Here’s what you can expect:

• Unlimited CI/CD minutes: run your pipelines as often as you need, with no per-minute billing or unexpected charges.
• Multiple concurrent jobs: speed up your development by running several jobs in parallel.
• The Docker executor with Docker-in-Docker support: easily build and push container images as part of your CI/CD process.
• Works seamlessly with both GitLab.com and self-managed GitLab instances.
• A private, dedicated infrastructure with fast NVMe/SSD storage ensures stable and predictable build performance.
• Available in 🇪🇺 Europe and 🇺🇸 USA regions to meet your team’s requirements.

Save time: you can 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 details:

• GitLab URL: Use https://gitlab.com for GitLab.com, or the URL of your self-managed GitLab instance. (If you are running GitLab on Stackhero, this might be https://git.your-company.com.)
• Runner authentication token (glrt-...) obtained in Step 2.
• Number of concurrent jobs you wish to allow.

Once you have saved your configuration, your runner will connect to GitLab and appear as online on the Runners page where you set it up.