DevOps & Cloud · CI failure diagnosis
PipelineDoctor
From failed job to the fix.
When a CI job fails, get the cause, the log lines that prove it, whose problem it is and the fix, across GitHub Actions, GitLab CI and Jenkins.
$ pipeline-doctor gitlab-missing-variable.log
pipeline-doctor: A required secret or variable is empty (high confidence)
GitLab CI, failed in step "step script" (lines 14–24), exit code 1
L22: KeyError: 'STAGING_DEPLOY_TOKEN'
Fix: Check the CI/CD variable `STAGING_DEPLOY_TOKEN` exists. Protected variables are only set on protected branches and tags.
Was this right? pipeline-doctor feedback fa54574d2336 --right|--wrong
The problem
Someone scrolls through a 5,000-line log to find out the variable was protected, the lockfile was stale or the runner ran out of memory. Every team does this several times a week.
What it does
Reads GitHub Actions, GitLab CI and Jenkins logs, finds the failing step and its exit code
About 30 failure types: tests, compile, lint, lockfiles, dependencies, secrets, token permissions, YAML, memory, disk, timeouts, runners, rate limits, TLS, Docker, Terraform, Kubernetes
Every cause cites the exact log lines, with a confidence score
Says whose problem it is (code, pipeline settings or runner) and whether a re-run is worth trying
Remembers past failures: "last time this was the protected variable"
"Was this right?" feedback and accuracy per rule
Fetches failed jobs directly from GitHub, GitLab and Jenkins; GitHub Action writes the diagnosis to the run summary
Secrets masked in every report; optional Claude explanation gets a redacted excerpt only
How it works
- Paste the log, or point it at a failed run
- Read the cause, the evidence lines and the fix
- Mark it right or wrong so accuracy is measured
Works with
Runs in your CI
diagnose:
needs: [build, test]
if: failure()
runs-on: ubuntu-latest
permissions: { actions: read }
steps:
- uses: Deepanshu18Saini/pipeline-doctor@main
Your data
- Secrets in logs are masked in every report.
- The optional Claude explanation sees a redacted excerpt only.
- Runs on your machine or in your CI.
Who it's for
Questions
Is it just a log summariser?
No. It applies rules with evidence, separates the root cause from knock-on errors, and says whether a re-run will help.
How do we know it's right?
Every diagnosis shows its evidence, and your feedback measures its accuracy over time.
Related
Often used with PipelineDoctor
BlastRadar
Change impact analysisKnow what a change will touch. Before a release, see every service a change can affect and the line of code that links it. After the release, confirm those services are still healthy.
$300–600 (₹10,000–20,000 in India)View product → DevOps & CloudSLOStudio
SLOs and error budgetsReliability you can measure. Define each SLO in a few lines and get correct burn-rate alerts, an error budget everyone understands, and a release gate, on the monitoring you already run.
$1,500–3,000 (₹40,000–80,000 in India)View product → DevOps & CloudTestScope
Test impact selectionRun the tests that matter. Every pull request runs the tests its change can affect, each with a stated reason, and the full suite whenever a change is too broad to trust.
$1,000–2,500 (₹25,000–60,000 in India)View product →See PipelineDoctor on your own data
A 30-minute call. We run the product on your export, repository or document and walk you through the results.