Connect Bitbucket Pipelines with Unblocked to analyze CI failures

Bitbucket Pipelines supplies the build evidence needed to understand whether a pull-request failure comes from the proposed change, the test environment, or an existing dependency. Unblocked combines that evidence with repository context before posting a confidence-gated report.

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.

Reports are posted as a comment on the pull request and are gated by confidence. Bitbucket posts on behalf of a bot account, so you set up (or reuse) an Unblocked bot user during configuration.

What you get

• Automatic failure analysis — The CI Failure Agent reads failed Bitbucket Pipelines builds and analyzes the logs 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.
• Grounded in your codebase — Analysis draws on your indexed code, pull requests, and discussions, so suggestions fit how your project actually works.
• 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 Bitbucket source code connected to Unblocked — the CI Failure Agent runs on your connected repositories.
• A Bitbucket bot account to post CI reports (invited to your workspace), or an existing bot account you can reuse.

Connect Bitbucket Pipelines to Unblocked

1. In Unblocked, open Settings → Continuous Integration and click Add CI Provider.
2. Click the Bitbucket Pipelines tile, then click Select Repositories and toggle the repositories where you want the CI Failure Agent enabled.
3. Set up a bot account: create a Bitbucket account named Unblocked, then sign in as a workspace admin and invite it to your workspace.
4. Select the bot account in Unblocked and authorize it if prompted, then click Save Settings.

Examples of Bitbucket Pipelines failures the CI Failure Agent can investigate:

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