Jenkins
Jenkins build troubleshooting, traced to the change
Intellira reads build info, console logs and test results read-only and connects a failing or stuck pipeline to the triggering commit — so you fix the cause, not the symptom.
Build & stage signals
Reads console logs, test results and build metadata to locate the failing stage.
Sub-job awareness
Understands pipeline stages vs sub-jobs and retrieves the right logs for each.
Commit correlation
Ties the failure to the change that triggered the build.
Jenkins errors Intellira diagnoses
Browse all guides →AgentOffline
A Jenkins agent shows offline and will not connect. Separate transport, secret, JDK, host, label, and cloud causes — then diagnose and fix each.
BuildFailure
A Jenkins build that fails at a stage needs the right log, not the whole console. Find the failing stage, tell FAILURE from UNSTABLE, and trace the change.
ExecutorStarvation
Jobs sit in the queue waiting for an executor. Separate true starvation from label mismatch, blocked builds, throttling, and flyweight waits — then clear it.
Common questions
Does it work with pipelines and freestyle jobs?
See Jenkins Analysis on your stack
Connect read-only and get an evidence-backed root cause on your next incident.