Guides
How to alert on CI regressions
A change makes CI 40% slower and it goes unnoticed for weeks.
4 min read
A change makes CI 40% slower and it goes unnoticed for weeks.
Why it happens
Nothing watches build duration, so regressions only surface as complaints.
How to fix it
- Alert on p95 duration increasing beyond a threshold week over week
- Alert on cache hit rate dropping — usually the leading indicator
- Route alerts to the team that owns the workflow, not to a general channel
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 collect runner metricsYou cannot tell whether a job is CPU-bound, memory-bound or disk-bound.How to track build duration percentilesAverage build time looks fine but developers still complain.How to export CI traces with OpenTelemetryCI timing data lives in a separate tool from the rest of your observability.How to query CI data programmaticallyYou need CI data in a dashboard or a weekly report.