Guides
How to set a CI minutes budget
Spend is discovered at the end of the month rather than controlled during it.
4 min read
Spend is discovered at the end of the month rather than controlled during it.
Why it happens
Alerts fire after the money is spent, and there is no enforcement mechanism.
How to fix it
- Set a hard cap that stops scheduling, not just an alert
- Budget per repository, since one repository usually dominates
- Alert at 50% and 80% so there is time to react
- Review the cap quarterly against merge volume, not headcount
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 attribute CI cost to teamsCI spend is one line on the invoice and no team feels responsible for it.When larger runners actually save moneyA larger runner costs more per minute, so it is unclear whether it is cheaper overall.