Guides
How to stop CI rerun storms
Developers rerun failing jobs repeatedly, multiplying cost and hiding real failures.
4 min read
Developers rerun failing jobs repeatedly, multiplying cost and hiding real failures.
Why it happens
Flaky tests train people to retry rather than investigate, and nothing limits how often they can.
How to fix it
- Track flake rate per test and quarantine the worst offenders
- Make rerun require a reason, or limit automatic retries to network steps
- Report the cost of reruns per repository so the incentive is visible
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 speed up GitHub ActionsYour pipeline takes longer than anyone wants to wait, and it is not obvious where the time goes.How to find the slow step in a workflowThe pipeline is slow but every individual step looks reasonable.How to reduce GitHub Actions cold startsJobs sit for 30 to 90 seconds before the first step runs.How to diagnose GitHub Actions queue timesJobs are queued for minutes before a runner picks them up.