Guides
How to design a runner label strategy
Labels grew organically and nobody knows which to use.
5 min read
Labels grew organically and nobody knows which to use.
Why it happens
Ad-hoc labels mean teams pick defensively large runners and cost drifts upward.
How to fix it
- Encode OS, architecture and size in a consistent scheme
- Publish a short table mapping workload type to recommended label
- Audit label usage quarterly and retire unused ones
- Use distinct labels per team where you need cost attribution
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 use runner groupsAny repository can schedule jobs on any runner.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.