You can now filter flaky tests by branch using the Test Analytics UI or API.

The filter will limit the list of flaky tests to those for which a flake has been detected one or more times on the selected branch.

To learn more, check out the API documentation.

You can now filter your tests on the Test and Flaky test pages by owner.

• owner:team-slug
• owner:team-slug-1,team-slug-2
• owner:none

You can now view your builds on an interactive canvas. The build canvas makes it easier to visualize your pipelines, understand running order and dependencies, and troubleshoot issues. It's available from the Canvas tab on build pages.

You can follow the progress of a running build by selecting Follow mode or pressing j:

Troubleshoot and investigate failed jobs by selecting Go to failure or pressing f:

Hover over a step to see further details and navigate to the logs:

For all the information about the build canvas and a demo of the key features, see Visualize your CI/CD pipeline on a canvas.

If you have feedback or suggestions, please contact support.

You can now search for test suites by name or slug directly from the Suites page. This feature makes finding the suite you're looking for simpler, especially when you track many suites. Happy searching!

A new version of the Buildkite CLI (bk) is now available in beta. 🎉

With bk, you can view, create, cancel, and unblock your builds from the command line. You can also stop agents in bulk.

For more details and installation instructions, see the documentation. If you have feedback or run into issues, please create a GitHub issue.

Teams can now schedule a weekly email summarizing their most flaky tests for the last 7 days. This summary will only include flaky tests assigned to the selected team. Either manually assign flaky tests, or check out the test owners feature to automate this process.

Users can create and manage these notifications from the suite settings page.

You can now resolve a flaky test within the flaky management dropdown.

To learn more about flaky resolution, check out the documentation.

You can now view the full logs for a job in the Buildkite Pipelines UI.

This change standardizes the options to view the full job logs:

• Open: Opens a human-readable version of the logs in a new tab.
• Download: Downloads the raw logs to your device.

To open the full logs for a job in the UI:

1. Expand a job row on a build.

2. Select Open.

   

3. View the full logs:

   

This feature will be turned on for all organizations in July 2024. If you would like early access to it, please contact support.

When builds start with a block or input step, you can now provide the values from the New Build modal and the API.

Previously, you had to start the build and provide inputs when the corresponding step ran. With this change, the input options are shown in the New Build modal and can be included in the API.

This change only shows when a block or input step is the first step in a pipeline, and the build is started from the Buildkite Pipelines UI or API. If the build starts from a Git webhook or you don't provide the values in the API, block and input steps behave as before—pausing the build until they receive the required values.

For example, the following pipeline starts with an input step:

So, the New Build modal looks like:

This feature will be turned on for all organizations in July 2024. If you would like early access to it, please contact support.

The build row is now easier to parse with updates to where key details appear, including:

• Showing the running time under the build status.
• Displaying the build number under the heading.
• Adding profile pictures to user details.
• Making the expansion areas on each row clearer with more defined click areas.

Previously, the build list looked like:

The new build list looks like:

You can now more easily identify steps that are pending or in an unexpected state while a build is running.

This change came from customer feedback about the build header placing too much prominence on steps that don’t cause pipelines to fail, such as steps that have passed or soft failed. Steps in these states are expected and generally don’t require immediate attention.

Thank you to the customers who worked alongside us on this small but impactful improvement. Please continue to reach out with your feedback and suggestions!

You can now view missing dependencies in job rows. This allows you to quickly debug your pipeline configuration while the build is running or after it fails.

When a build is running, and a job has a dependency that doesn't exist yet, you'll see the following message:

You can expand the job row to see the names of the missing dependencies:

If the step dependency is not resolved and the build fails, you'll see an error message:

When you expand the job row, you'll see the names of the missing dependencies:

You can now add line breaks to your block and input steps in Buildkite Pipelines. For example, see the prompt and hint fields in the following pipeline definition:

These fields are displayed in the UI as follows:

When viewing jobs, the links to agent and queue details now take up less space, and you can see the full command on hover when it's truncated.

A recent change added links from jobs to agent and queue details, but the links took up a significant portion of the job row. We've made the links more compact so you can see more of the job name and command while keeping direct links to the agent and queue details:

When a longer job command is truncated, you can now see the full command on hover:

You can now retry failed builds directly from the build view.

If any jobs fail while a build is running, you will now see a Retry failed jobs button in the build header. This allows you to retry all failed jobs at once rather than selecting Retry on individual jobs.

After a build finishes, the Retry failed jobs button now displays directly in the build header rather than under the Rebuild menu.

You can now search for tests by name, scope, and location from the Tests page.

You can now search for flaky tests by test name, scope, and location using the Test Analytics UI or API.

To learn more, check out the API documentation.

Users on our Pro and Enterprise plans can assign flaky tests to teams in their organization. Use flaky test assignment to signal to other teams that a flaky test is being worked on.

To learn more, check out the documentation.

The waterfall view has been updated to help you debug builds faster.

You can now go directly from a job in the waterfall view:

To its log output:

Buildkite Teams can be accessed programmatically through the REST API, improving parity with our existing GraphQL API.

Explore further details and learn how to integrate with our API documentation.