Connect GitLab Pipelines with Unblocked to analyze CI failures

GitLab Pipelines adds failed-job evidence to the code and merge-request context Unblocked already has. The CI Failure Agent uses those signals together to explain a likely root cause and place the result where the team is already reviewing the change.

Because Unblocked already understands your codebase, merge 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 merge request and are gated by confidence. GitLab 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 GitLab pipeline runs and analyzes the logs to find the root cause — no manual log-digging.
• Root-cause reports on the MR — When confident, Unblocked posts a comment on the merge request explaining the failure and suggesting a fix.
• Grounded in your codebase — Analysis draws on your indexed code, merge 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 MRs 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 GitLab source code connected to Unblocked — the CI Failure Agent runs on your connected projects.
• A GitLab bot account to post CI reports (Planner role or above on the group), or an existing bot account you can reuse.

Connect GitLab Pipelines to Unblocked

1. In Unblocked, open Settings → Continuous Integration and click Add a CI Provider.
2. Click the GitLab Pipelines tile, then click Select Repositories and toggle the projects where you want the CI Failure Agent enabled.
3. Set up a bot account: create (or reuse) a GitLab user named Unblocked, sign in as a group admin, and invite it to your group with the Planner role or above.
4. Select the bot account in Unblocked and authorize it (you must be signed in to GitLab as that account), then click Save Settings.

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

• Why did the GitLab pipeline fail on this merge request?
• What is the root cause of the failing job in CI?
• Which recent change most likely caused the pipeline failure?