Unblocked for CI
Automatically analyze CI failures and get actionable fix suggestions
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, 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 GitHub Actions. CircleCI and Buildkite are coming soon.
Configuring GitHub Actions
To connect GitHub Actions to Unblocked, follow these steps:
Add CI Data Source
In the left sidebar, click on Data Sources. Then click on the Add Source tab and choose Continuous Integration.
Connect GitHub Actions
Click on the GitHub Actions tile.
Configure GitHub Actions
You may be prompted to accept additional permissions in GitHub if you haven’t already. Click Select Repositories to choose the repositories you want to enable CI triage on.
Select Repositories
Toggle the repositories you want to enable by selecting the CI Triage switch.
Done
Click Save Settings to apply your changes. Now Unblocked will analyze CI 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:
- Navigate to Settings in your Unblocked dashboard
- Select Preferences under the Personal Settings section
- 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.