GitLab Runner: 3. Choose an instance size and a region

This documentation is part of the Automate with the CLI guide. You can view the complete guide here: Start GitLab-Runner, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI.

👋 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!

# List instance sizes for your service store (use the NAME column for --instance)
stackhero instances-store-list --service-store=gitlab-runner

# List available regions (names such as "europe")
stackhero regions-list

Continue reading this guide

  1. Read the full guide: Automate with the CLI
    Start GitLab-Runner, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI
  2. 1. Authenticate
  3. 2. Find the GitLab-Runner service store
  4. 4. Create the service
  5. 5. Retrieve credentials
  6. 6. Change the configuration

Other articles for GitLab Runner

  1. Getting started
    Connect your Stackhero GitLab Runner to GitLab.com or a self-hosted GitLab and run your first pipeline
  2. Building Docker images
    Build and push Docker images from your GitLab CI/CD pipelines using your Stackhero runner and Docker-in-Docker