View as Markdown

CI Insights

Optimize your CI run time, catch flaky tests, and give developers actionable insights so your team ships code faster.


CI Insights helps you monitor your pipelines, detect flaky tests and jobs, and improve your CI efficiency. This guide walks you through enabling CI Insights via GitHub and covers basic configuration steps.

CI Insights flags a flaky job when the same job, in the same pipeline, runs more than once on the same commit (SHA1) and the runs end with different conclusions, even though the code did not change. Cancelled runs are ignored, since a cancellation says nothing about the code.

A flaky test comes from the same kind of disagreement between repeated runs of one commit, or from a test that keeps failing now and then on new commits. See Health Status for how a test moves between healthy, flaky, and broken.

To set up systematic flaky test detection in your CI pipeline, see our dedicated Flaky Test Detection guide.

Select your CI system below to enable CI Insights and configure flaky test detection.

To capture test-level data from your CI pipeline, configure your test framework to upload results to Mergify. See the Test Engine test framework guides for framework-specific setup instructions.

Was this page helpful?