Hi, I’d like to suggest Build Change Investigator for a future Plugin of the Month.
It’s a newer Jenkins plugin focused on one of the most time-consuming parts of CI troubleshooting: figuring out what changed when a build that was working suddenly starts failing.
Normally, an engineer may have to jump between Console Output, build history, Git commits, changed files, and source diffs just to work out where the regression may have started. Build Change Investigator brings that context together directly on the Jenkins build page.
It compares the failed build with the last known-good build, extracts the relevant failure signal, looks at the SCM changes introduced in that window, and ranks the changes that appear most related based on file, module, and stage context. When retained history supports it, it can also narrow down the first bad build.
The goal is to give engineers a much better starting point and reduce the amount of time spent manually digging through logs and cross-referencing builds. It still keeps the full evidence available and does not claim to automatically prove the root cause.
The plugin also supports build-to-build comparison, similar past failure context, and a copyable investigation summary for sharing findings with teammates.
AI is optional. The main investigation works without it. If an administrator configures an AI provider, an authorized user can ask it to interpret the collected evidence and suggest what to check next, while keeping that interpretation separate from the deterministic evidence.
It currently supports OpenAI, Anthropic Claude, AWS Bedrock, Azure OpenAI, Google Gemini, Ollama, and OpenAI-compatible endpoints.
Official Jenkins plugin:
Source:
I’d be happy to provide screenshots, examples, or any additional information if it would be useful for consideration.