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

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

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 use the store name gitlab-runner in subsequent commands, or select a specific svs-xxxxxx ID from the list if you prefer.