Failure Analysis
How Failure Analysis Works#
CI/CD pipeline failures are one of the biggest drains on engineering time. On average, developers spend 30–45 minutes per incident parsing logs, searching error messages, and bisecting recent commits. Codluma reduces this to under 10 seconds.
Full log analysis
The entire pipeline log is sent for analysis — including multi-step builds with parallel jobs.
Commit attribution
Codluma identifies which specific commit or file change introduced the failure.
Pattern memory
Recurring failure patterns across your org are detected and flagged with historical context.
Step-by-step fix
Every analysis ends with concrete, numbered remediation steps — not just an explanation.
The analysis pipeline
Failure event received
A CI/CD webhook fires when a pipeline job or workflow fails. Codluma receives the event with the job ID and pipeline metadata.
Log retrieval
Codluma fetches the full raw log via the CI/CD provider API. Logs up to 2 MB are processed in full; larger logs are truncated to the last 500 lines plus all error lines.
Error extraction
A deterministic parser identifies error lines, exit codes, stack traces, and known error signatures (npm ERR!, ECONNREFUSED, OOMKilled, etc.) before AI processing.
AI root-cause analysis
The extracted errors plus recent commit metadata (last 5 commits) are sent to Claude Sonnet 4.6. The model identifies the root cause, the likely offending commit, and generates a fix.
Result delivery
The analysis is posted as a comment on the triggering commit or PR, shown in the dashboard, and optionally sent to Slack/Teams.
Supported CI/CD Providers#
Codluma supports all major CI/CD platforms. Each integration handles platform-specific log formats and API authentication independently.
Jenkins setup
Jenkins requires the Codluma Notification Plugin. Install it from the Jenkins Plugin Manager or by adding the following to your plugins.txt:
reviewops-ai-notifier:1.4.2
Then add a post-build step in your Jenkinsfile:
post {
failure {
reviewopsNotify(
apiKey: credentials('REVIEWOPS_API_KEY'),
projectId: env.REVIEWOPS_PROJECT_ID
)
}
}Log Redaction Levels#
Before any log content is sent for AI analysis, Codluma applies configurable redaction to protect secrets, PII, and internal infrastructure details. Set the level per repository under Settings → Failure Analysis → Redaction.
Warning
Failure Categories#
Every failure analysis is classified into one of eight categories. Categories appear in the dashboard and can be used to filter and trend your failure data over time.
Tip
Reading Fix Suggestions#
Every failure analysis ends with a structured fix suggestion containing four parts:
Root cause
A single-sentence explanation of the underlying failure reason — not just the error message, but why it occurred.
Offending change
The specific commit SHA, file, and line that introduced the failure, when the model can determine it from the log and commit history.
Fix steps
Numbered, actionable remediation steps. Commands are copy-pasteable. File paths are relative to the repository root.
Prevention note
A brief note on how to prevent this class of failure in future — e.g. adding a dependency audit to CI or pinning a version.
Example analysis output
Root cause
Peer dependency conflict: @stripe/react-stripe-js@2.4.0 requires
react@>=18.0.0 but package-lock.json pins react@17.0.2.
Offending change
Commit a4f2c1d by @james-wu 2 hours ago
File: package.json — @stripe/react-stripe-js bumped from 1.10.0 → 2.4.0
Fix steps
1. Upgrade React to 18:
npm install react@18 react-dom@18 --save-exact
2. Update TypeScript types:
npm install @types/react@18 @types/react-dom@18 --save-dev
3. Regenerate the lockfile:
npm install
4. Run your test suite to verify React 18 compatibility:
npm test
Prevention
Add "engines": { "react": ">=18" } to package.json and run
npm audit on every dependency bump in CI to catch peer conflicts early.Tip
Can't find what you need?
Contact support