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