Unblocked for CI is currently in early access beta. Reach out if you are interested in participating.

Overview

Debugging CI (Continuous Integration) failures in pull requests can be time-consuming and complex. Unblocked streamlines this process by automatically analyzing failure logs and providing actionable fix suggestions when it has high confidence in the root cause of the failure. When a CI job fails on a pull request, Unblocked will post a report as a comment in your pull request, helping you quickly identify and resolve the issue.

Connecting CI Systems

Today Unblocked supports Buildkite, CircleCI, and GitHub Actions. Bitbucket Pipelines and other CI systems are coming soon. Select the CI system you’d like to configure:

Configuring Buildkite

To connect Buildkite to Unblocked, follow these steps:

1

Add CI Data Source

In the left sidebar, click on Data Sources. Then click on Add another data source and choose Continuous Integration.

2

Connect Buildkite

Click on the Buildkite tile.

3

Authorize Your Buildkite Account

  • Create a new API Access Token in Buildkite:

  • Enter “Unblocked” as the Description.

  • Choose the appropriate organization in Organization Access.

  • Select the following REST API Scopes:

    • read_build_logs
    • read_builds
    • read_organizations
    • read_pipelines
    • read_user
  • Copy the following CIDR ranges into Allowed IP Addresses:

    • 34.212.246.90/32
    • 44.235.109.70/32
    • 44.236.252.193/32
    • 52.88.232.82/32
  • Click Create New API Access Token.

4

Add a Buildkite Webhook

  • Go to the Notification Services page.

  • Click Add Webhook.

  • In the description field, enter “Unblocked”.

  • Copy and Paste the Webhook URL and Token from Unblocked into the corresponding fields in Buildkite.

  • Select the following events:

    • build-finished
    • job-finished
  • Ensure that All Pipelines are selected.

  • Leave Branch filtering blank.

  • Click Add Webhook Notification.

5

Select Repositories

Toggle the repositories you want to enable by selecting them.

6

Done

Click Save Settings to apply your changes. Now Unblocked will analyze Buildkite failures in the selected repositories and post reports to pull requests.

Configuring CI Triage in Personal Settings

By default, Unblocked will post reports for all developers in your organization when it has high confidence in the root cause of a CI failure. As a developer, you can control this behavior for your pull requests:

  1. Navigate to Settings in your Unblocked dashboard
  2. Select Preferences under the Personal Settings section
  3. Locate the CI Triage toggle and set it according to your preference

This setting applies only to your pull requests, allowing you to customize your workflow while respecting team preferences.