On the build page, jobs waiting on a concurrency group now show a list of the jobs ahead of them in the group.

This list gives you visibility into how soon the current job might run and which jobs are backing up a concurrency group.

For more information on concurrency groups, see the documentation.

You can now view unique flaky test metrics on the suite summary page. This metric reflects the number of unique tests that have been flaky over a given period.

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.

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.

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.

You can now use Test Analytics to manage your Cypress test suites. With the JavaScript test collector configured, Cypress test results are automatically sent to Test Analytics to give you insights into your test suite.

Check out the docs to learn more about configuring Test Analytics with Cypress.

You can now go directly from jobs to agent details. When viewing a build, you'll see each job with its agent's name and a link to the agent details:

If you're using clusters, you'll see a link to the queue for the job while waiting for an agent to be assigned:

Once the job is assigned to an agent, you'll see the agent details alongside the queue:

Clusters will be enabled for all organizations on 26 February, 2024.

Clusters is a Buildkite feature used to manage and organize agents and queues, which:

• allows teams to self-manage their Buildkite agent pools,
• allows admins to create isolated sets of agents and pipelines within within a single Buildkite organization,
• helps make agents and queues more discoverable across your organization, and
• provides easily accessible queue metrics.

After the release all existing agents can be accessed through Unclustered grouping on the agents page.

Learn more about clusters

Access tokens for agents will now be limited to the lifetime of the job. There is now a unique BUILDKITE_AGENT_ACCESS_TOKEN for each job that is run, which will stop working once the job finishes. This reduces the period of impact to the lifetime of the job if a BUILDKITE_AGENT_ACCESS_TOKEN is leaked from the agent’s environment.

Ensure you are running Buildkite Agent version v3.39.0 or later to take advantage of these tokens and v3.62.0 for all the latest improvements.

For more details, see the documentation.