GitLab Runner: Introduction
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!
A GitLab Runner is the agent responsible for executing your GitLab CI/CD jobs. Each time a pipeline runs, the runner picks up each job, executes it inside an isolated Docker container, and then reports the results back to GitLab.
With Stackhero, your runner always operates on private, dedicated infrastructure. There are no per-minute charges or usage quotas: your CI/CD minutes are unlimited. Depending on your plan, your runner can handle multiple concurrent jobs in parallel, making it easy to scale your build throughput.
This guide will help you connect your Stackhero runner to GitLab and get your first pipeline running quickly.