GitLab Runner: 2. Find the GitLab-Runner service store

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!

Next, you will want to list the GitLab-Runner service stores available to your account. The CLI accepts the store name (gitlab-runner) directly, so there is no need to look up or copy any IDs.

# List GitLab-Runner service stores (add --organization if you manage more than one)
stackhero services-store-list --name="gitlab-runner"

You can refer to the store name gitlab-runner in subsequent commands, or choose a specific svs-xxxxxx ID from the list if you prefer.