Guides
How to attribute CI cost to teams
CI spend is one line on the invoice and no team feels responsible for it.
5 min read
CI spend is one line on the invoice and no team feels responsible for it.
Why it happens
Without per-team attribution there is no feedback loop between the team that adds a job and the budget it consumes.
How to fix it
- Break spend down by repository, then map repositories to owning teams
- Use distinct runner labels per team where a shared repository serves several
- Publish a monthly report per team rather than one global number
- Set per-repository budget caps so a runaway job is bounded
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 reduce GitHub Actions costsThe CI bill grows faster than the team and nobody is sure why.How to measure CI cost per pull requestYou know the monthly total but not what a single pull request costs.How to set a CI minutes budgetSpend is discovered at the end of the month rather than controlled during it.When larger runners actually save moneyA larger runner costs more per minute, so it is unclear whether it is cheaper overall.