---
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 optimize
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 refresh this page to view jobs & tests.

## Understanding CI Insights

### Components

<DocsetGrid>
  <Docset
    title="Runners"
    path="/ci-insights/runners"
    icon="lucide:server"
  >
    Track runner fleet performance, queue times, 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 automatically detects flaky behavior in both jobs and tests using the same criteria:

A **flaky job** or **flaky test** is one that has 2 different conclusions on
the same SHA1. For example, if a job or test runs twice on the same commit and
once fails while the other succeeds, it's considered flaky because the outcome
is not consistent with the same code.

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.