---
title: CI Insights
description: Optimize your CI run time, catch flaky tests, and give developers actionable insights so your team ships code faster.
hubAccent: true
---

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.

> First time here? Follow these 3 steps to see data fast:
> 1. Install the Mergify GitHub App on a repo with existing CI.
> 2. Ensure your tests produce a supported format (JUnit XML, pytest, Jest, etc.); pick a framework below if needed.
> 3. Re-run a workflow (or push a trivial commit), then open CI Insights in the dashboard to view your jobs and tests.

## Understanding CI Insights

### Components

<DocsetGrid>
  <Docset
    title="Self-hosted runners"
    path="/ci-insights/runners"
    icon="lucide:server"
  >
    Monitor your self-hosted runners' capacity, performance, cost, and reliability.
  </Docset>
  <Docset
    title="Jobs"
    path="/ci-insights/jobs"
    icon="lucide:list-checks"
  >
    Monitor job health, duration, cost, and flaky behavior.
  </Docset>
  <Docset
    title="Auto-Retry"
    path="/ci-insights/auto-retry"
    icon="lucide:rotate-cw"
  >
    Automatically retry failed CI jobs caused by flaky tests or transient failures.
  </Docset>
</DocsetGrid>

### Flaky Detection

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

Tests use the same rule, with one addition: a **flaky test** has to have failed
on some runs of a commit and passed on others. A test that is skipped in one
run and passes in another stays healthy.

To set up systematic flaky test detection in your CI pipeline, see our
dedicated [Flaky Test Detection guide](/ci-insights/flaky-test-detection).

## CI Setup Guides

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

<DocsetGrid>
  <Docset
    title="Buildkite"
    path="/ci-insights/setup/buildkite"
    icon="simple-icons:buildkite"
  >
    Enable CI Insights & flaky test detection for Buildkite.
  </Docset>
  <Docset
    title="GitHub Actions"
    path="/ci-insights/setup/github-actions"
    icon="simple-icons:githubactions"
  >
    Enable CI Insights & flaky test detection for GitHub Actions.
  </Docset>
  <Docset
    title="Jenkins"
    path="/ci-insights/setup/jenkins"
    icon="simple-icons:jenkins"
  >
    Enable CI Insights & flaky test detection for Jenkins.
  </Docset>
</DocsetGrid>

## Test Framework Configuration

To capture test-level data from your CI pipeline, configure your test
framework to upload results to Mergify. See the
[Test Insights test framework guides](/test-insights#test-framework-configuration)
for framework-specific setup instructions.