RAG for Jenkins: retrieving diagnostics after a failed build
RAG for Jenkins and Ansible: every failed build triggers the delivery of source-backed diagnostics. An AI agent can attempt a fix and rerun the build at the developer’s request.
The need
After a failed build, a developer needs useful diagnostic information. This work connects Jenkins and Ansible to a RAG mechanism for retrieving source-backed diagnostics.
How it works
Every build failure triggers delivery of diagnostics. RAG retrieves available information to provide context to the developer and the AI agent.
Human control
An AI agent can attempt a fix and rerun the build at the developer’s request. This request is the control point described in the case study published on Malt. The diagram illustrates the operating principle.