CI/CD Pipeline Analysis

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, 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

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

​

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