Get This Tool
CI-medic
Summary
CI failure logs are mostly noise — stack traces, retry attempts, environment dumps — and finding the one line that actually broke the build costs real time on every red pipeline.
ci-medic is an open-source CLI and CI integration that runs automatically on pipeline failure, strips that noise down to the root cause, classifies it into one of five categories (code, flake, infra, dependency, or config), and posts the verdict where your team already looks — a sticky PR comment on GitHub Actions or a build description update on Jenkins. Secrets are redacted before any model sees the log. You can point it at a local model and logs never leave your network. The tool does one thing on one trigger: failure fires, logs go in, structured verdict comes out. There is no dashboard, no retention, no analytics — just the signal.
Bottom line: Pick this if your team wastes time hunting root causes in noisy GitHub Actions or Jenkins logs and needs a privacy-safe, zero-cost way to surface them automatically — but don't expect it to cover pipelines beyond those two platforms without dropping to the CLI.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Automatic failure-triggered analysis, so engineers stop spending the first five minutes of every incident scrolling logs to find the line that actually broke the build.
- Five-category classification (code, flake, infra, dependency, config) posted directly into the PR comment or build description, so the verdict is already waiting in the place the team is already looking.
- Secret redaction before any model sees the log, which means teams with compliance requirements can run AI triage without sending raw pipeline output to an external API.
- Local LLM routing supported, so logs never leave your network — the difference between a tool your security team approves and one they block.
- Apache-2.0 license with pip install and Docker support, so there is no vendor lock-in and no cost gate between installation and a working verdict.
Cons
Sign in to edit- Native automated integration covers only GitHub Actions and Jenkins — teams on CircleCI, GitLab CI, or Bitbucket Pipelines lose the on-failure trigger and must run the CLI manually or write their own wrapper, at which point they are maintaining glue code on top of the tool.
- No aggregation or trend layer: ci-medic classifies individual failures but does not surface patterns across runs — a team trying to identify which test is responsible for repeated flake failures across a sprint still needs a separate observability or test analytics tool.
- A team that needs failure triage integrated with incident management, alert routing, or a shared error dashboard will hit the tool's boundary fast — ci-medic posts a comment and stops there, so teams with those requirements will evaluate purpose-built CI observability platforms instead.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- GitHub Actions, Jenkins, CLI
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-06-28T02:25:14.026Z
Best For
Who it's for
- Teams running GitHub Actions or Jenkins pipelines
- Environments requiring log privacy and secret redaction
- Users wanting automatic error classification without manual review
What it does well
- Triage failed GitHub Actions jobs with AI verdicts in PR comments
- Classify Jenkins build failures and update descriptions automatically
- Analyze local CI log files via CLI for any platform
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare CI-medic
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is CI-medic free?
- Yes — CI-medic is fully free to use. There is no paid tier.
- Is CI-medic open source?
- Yes. CI-medic is open source.
- Can I self-host CI-medic?
- Yes. CI-medic supports self-hosting on your own infrastructure.
- What platforms does CI-medic support?
- CI-medic is available on: GitHub Actions, Jenkins, CLI.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Most CI failure triage happens the same way: someone clicks into a 4,000-line log, scrolls past the noise, and eventually finds the line that actually broke the build. ci-medic automates that step. When a pipeline fails, ci-medic reads the full log, identifies the real error, redacts any secrets it finds, and classifies the failure into one of five categories — code, flake, infra, dependency, or config — then posts a structured verdict directly into the PR comment thread on GitHub Actions or the build description field on Jenkins. No manual trigger, no separate dashboard to check.
The privacy-first architecture is the distinguishing design choice. The vendor states that secrets are redacted before any model sees the log, and the docs describe a self-hosted path where you point ci-medic at a local LLM, which means log contents never leave your network. For teams in regulated environments where shipping raw CI logs to a third-party API is a non-starter, that is the feature that makes this usable at all.
ci-medic fits tightly into two scenarios: GitHub Actions pipelines where you want a verdict in the PR comment without building a custom action, and Jenkins environments where manual log review is the current process. The CLI mode extends it to any local log file on any platform. Where it breaks: there is no native integration for CircleCI, GitLab CI, Bitbucket Pipelines, or other platforms — teams on those pipelines use the CLI manually or write their own wrapper, which means the automated-on-failure trigger disappears. There is also no aggregation layer, so spotting a pattern of flake failures across dozens of PRs over time requires a separate tool.
Installation is via pip, Docker support is included, and the project is licensed under Apache-2.0. An AI verdict requires an API key for a hosted model, but the vendor states local model routing is supported, making the hosted key optional. The GitHub Actions integration is defined in action.yml and described as zero-setup for that platform; Jenkins requires a one-time configuration step to enable build description updates.