# CI Visibility: monitor the pipeline like production

CI is a production system for developers. When it degrades, every team degrades. CI Visibility brings pipeline and test results into Datadog so you can treat it that way.

## Setup

1. Connect the CI provider (the docs list providers: GitHub Actions, GitLab, Jenkins, CircleCI, Buildkite, and more). Follow the provider page for your stack.
2. Instrument the pipeline so stages and jobs are traced as they execute: you get duration breakdowns per stage, not just pass/fail.
3. Enable test visibility: per-test results, durations, and flakiness history.

## What to do with it

- **Flaky test list**: the single highest-value view. Sort by flakiness, fix or quarantine from the top. A flaky test suite trains developers to ignore red, which is how real breakages ship.
- **Pipeline duration trends**: alert when p95 pipeline time regresses. Slow CI is a tax on every commit; a 20-minute regression is a staffing decision in disguise.
- **Failure-to-commit correlation**: when a deploy breaks, trace back to the commit and the pipeline run that let it through. This closes the loop between CI signal and production incident.
- **Monitors on CI data**: failed pipeline rate, queue wait time. Page the platform team on the same terms as production.

## Verify

A merged PR shows its pipeline trace with stage timings. The flaky list is non-empty (it always is) and has an owner. One monitor exists on pipeline health and has fired at least once in testing.