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 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 expect:

  • 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 consistent, reliable builds.
  • Available in both 🇪🇺 Europe and 🇺🇸 USA regions.

Save time: connect your first GitLab Runner and start running pipelines in just a few minutes!

Want 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 or a self-hosted GitLab and run your first pipeline
  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 from your GitLab CI/CD pipelines using your Stackhero runner and Docker-in-Docker
  2. Automate with the CLI
    Start GitLab-Runner, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI