Guides
How to use runner groups
Any repository can schedule jobs on any runner.
4 min read
Any repository can schedule jobs on any runner.
Why it happens
Without groups there is no access boundary between low-trust repositories and privileged runners.
How to fix it
- Create groups per trust level and scope them to specific repositories
- Put runners with network access in their own restricted group
- Set per-group concurrency caps as a budget guardrail
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.How to use reusable workflows at scaleFifty repositories have fifty slightly different copies of the same pipeline.