CI/CD Pipeline Analysis

How CodeRabbit reads CI/CD pipeline failures and posts inline fix suggestions directly on the relevant lines of your pull request.

When a CI/CD pipeline fails on a pull request, CodeRabbit reads the failure output and posts inline comments with suggested fixes — directly on the lines of code that caused the failure.

This works across multiple CI/CD platforms: GitHub Actions, GitLab CI/CD, CircleCI, Jenkins, and Azure DevOps Pipelines.

How it works

1. A pull request is opened or updated and your CI/CD pipelines run.
2. CodeRabbit waits for pipeline results to become available.
3. CodeRabbit reads the failure logs and identifies the root cause.
4. Inline comments with suggested fixes are posted on the relevant lines of code.

Supported platforms

Platform	How CodeRabbit reads pipeline output
GitHub Actions	Via GitHub Checks
GitLab CI/CD	Via GitLab pipeline API, including GitLab Advanced Security SAST/DAST findings
CircleCI	Via CircleCI pipeline API (requires integration)
Jenkins	CodeRabbit reads failed or unstable Jenkins builds that match the exact pull-request head commit via the Jenkins JSON API (requires a Jenkins connection)
Azure DevOps Pipelines	Via Azure DevOps Checks API

For GitHub Actions specifically, pipeline analysis depends on the github-checks tool configuration.

Oversized GitHub Actions logs have coverage limits that can exclude earlier failure output. See GitHub Checks for the exact values.

What failures are analyzed

CI/CD pipeline analysis covers a broad range of failure types:

• Build failures — Docker, Node.js, Java, Python, Go module errors
• Test failures — unit, integration, and end-to-end test output
• Security scan findings — SAST and DAST output from tools like GitLab Advanced Security or custom pipeline steps
• Infrastructure-as-code validation — Terraform, Kubernetes, Ansible, and CloudFormation errors
• Linter and code quality output — any linter running as a pipeline step

Configuration

For GitHub Actions, use the github-checks tool configuration to control whether GitHub Checks data is included in reviews.

For all other platforms (GitLab, CircleCI, Azure DevOps), CodeRabbit reads pipeline output automatically with no additional configuration required.

What’s next

GitHub Checks configuration

Configure whether GitHub Actions check results are included in pipeline analysis.

CircleCI integration

Connect your CircleCI account so CodeRabbit can read pipeline failure logs and post inline fix suggestions.

Jenkins integration

Connect Jenkins so CodeRabbit can read matching build failures and test results.