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

This documentation is part of the Automate with the CLI guide. View the full guide here: Start GitLab-Runner, retrieve its credentials, and change its configuration programmatically with the Stackhero CLI.

👋 Welcome to the Stackhero documentation!

Stackhero gives you an easy-to-use GitLab Runner cloud solution designed to handle your GitLab CI/CD jobs efficiently. Here is what you can look forward to:

  • Unlimited CI/CD minutes: there is no per-minute billing, so your pipelines can run whenever you need them.
  • Multiple concurrent jobs: run several jobs at the same time to speed up your entire pipeline.
  • The Docker executor with Docker-in-Docker support: streamline 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: you can 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 like "europe")
stackhero regions-list

Continue reading this guide

  1. Read the full guide: Automate with the CLI
    Start GitLab-Runner, retrieve its credentials, and change its configuration programmatically with 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-managed 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