Connect Jenkins with Unblocked to analyze CI failures

Jenkins brings build evidence from your own CI environment into Unblocked’s failure-analysis workflow. That evidence is evaluated with the connected repository and pull request so the resulting report reflects the change under review, not only an isolated log line.

Because Unblocked already understands your codebase, pull requests, and team discussions, its analysis is grounded in that context — it explains what broke and suggests a fix, with links back to the relevant code and history.

Jenkins connects to your own server through the Unblocked Jenkins plugin and a personal access token. Reports post as a comment on the pull request and are gated by confidence.

What you get

• Automatic failure analysis — The CI Failure Agent analyzes failed Jenkins builds to find the root cause — no manual log-digging.
• Root-cause reports on the PR — When confident, Unblocked posts a comment on the pull request explaining the failure and suggesting a fix.
• Runs against your own server — The Unblocked Jenkins plugin connects to your self-hosted Jenkins instance, with IP-range allowlisting for network-restricted servers.
• Confidence-gated, per-developer control — Reports post only when Unblocked is highly confident, and each developer can toggle them for their own PRs in Personal Settings → Preferences.

Need screenshots or troubleshooting?This is a concise connection summary. Follow the complete setup guide ↗

Prerequisites

• An Unblocked account (free to start).
• Your source code connected to Unblocked — the CI Failure Agent runs on your connected repositories.
• A reachable Jenkins server and permission to install the Unblocked Jenkins plugin (allow Unblocked’s IP ranges if your server has restricted network access).

Connect Jenkins to Unblocked

1. In Unblocked, open Settings → Continuous Integration, click Add CI Provider, and click the Jenkins tile.
2. Enter your Jenkins server hostname or URL and click Verify (allow Unblocked’s IP ranges first if your server is network-restricted).
3. On your Jenkins server, install the "Unblocked" plugin, then enter a Jenkins username and create a Personal Access Token and paste it into Unblocked.
4. Toggle the repositories you want to enable, then click Save Settings.

Examples of Jenkins failures the CI Failure Agent can investigate:

• Why did the Jenkins build fail on this pull request?
• What is the root cause of the failing stage in CI?
• Which recent change most likely caused the build failure?