GitLab Runner: 1. Authenticate

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 provides a straightforward GitLab Runner cloud solution that makes running your GitLab CI/CD jobs efficient and hassle-free. Here is 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: accelerate 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 suit your team's needs.

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

The easiest way to get started is by logging in through your browser. When you run the login command, the CLI opens a web page where you can approve access. No passwords or 2FA codes are entered into the CLI itself.

stackhero login

After logging in, your credentials are stored locally and will be used automatically by future CLI commands.

For fully automated environments like scripts or CI pipelines, you might prefer a non-interactive access token. You can create one from your dashboard (Account > Access tokens), then export it as an environment variable. The CLI, and any script you run, will pick it up automatically.

export STACKHERO_TOKEN="usr-xxxxxx:your-token"