Guides
How to set CI service levels
Nobody agrees on how fast CI should be, so it never gets prioritised.
5 min read
Nobody agrees on how fast CI should be, so it never gets prioritised.
Why it happens
Without a target, CI speed loses to feature work every time.
How to fix it
- Set an explicit target, for example p95 pull-request feedback under ten minutes
- Report against it weekly
- Treat a sustained breach as a bug with an owner, not as background noise
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.