GitLab Runner: Next step

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!

If you would like to build and push Docker images from your pipelines, continue with Building Docker images.

Continue reading this guide

  1. Read the full guide: Getting started
    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
  2. Introduction
  3. Step 1: Create your GitLab Runner on Stackhero
  4. Step 2: Create a runner in GitLab
  5. Step 3: Connect your runner
  6. Step 4: Run your first pipeline

Other articles for GitLab Runner

  1. Building Docker images
    Build and push Docker images efficiently from your GitLab CI/CD pipelines using Stackhero runners and Docker-in-Docker
  2. Automate with the CLI
    Start GitLab-Runner, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI