The Bitbucket Cloud (BCLOUD) project is an invaluable source of customer-requested product features, enhancements, and suggestions. As Bitbucket Cloud has continued to grow, we’ve built up quite a backlog! To streamline the process, we recently implemented an in-product form as a replacement for manual issue submission. Entering feedback about Bitbucket Cloud is now easier than ever!

We are happy to announce that Bitbucket Pipelines now supports macOS self-hosted runners. We have moved from beta to an official release. You can now create a self-hosted runner and run it on your macOS infrastructure to run macOS and iOS builds. Since you’re using your own runner, you won't be charged for Bitbucket Pipelines build minutes.

Over the last few weeks, we’ve launched several new features like support for Docker BuildKit, the ability to set default PR tasks, and fixed a few bugs. Here are the updates.

We are happy to announce that Bitbucket Pipelines now supports non-containerized Linux Shell self-hosted runners. This is currently in beta. You can now create a self-hosted runner and run it on your Linux infrastructure without container restrictions. Since it is your infrastructure, you will not be charged for the build minutes used by your self-hosted runner.

We are introducing a change to the pull request merge checks that will make them more reliable. Specifically, we will no longer allow pull requests to be merged while a build is in progress. It was possible for a pull request to be merged while some of its builds were still in progress and for those builds to fail after the merge has completed. This created an undesirable situation if build merge checks were enabled.

There are multiple ways to create a task on a pull request. They can be added from the sidebar, top-level pull request comments, file-level comment or inline comments. Once created, they all appear in the sidebar. On any repository, merge checks can be configured for any branch to only allow merging if all pull request tasks are resolved. This is a very useful functionality if some tasks are critical to be resolved before changes are merged.

With support for Atlassian Server products ending in February 2024, many of you are likely evaluating or planning your migration to Bitbucket Cloud. To help you navigate the migration process, we've put together a list of frequently asked questions that we hear from customers. Each section below has several resource links to help you learn more and start planning your migration.

We are happy to announce that one of the top voted features for Bitbucket Pipelines, Docker BuildKit will be available next week. You can now build Docker images with the BuildKit utility. With BuildKit you can take advantage of the various features it provides like.

Bitbucket Cloud is making changes to pull request diff functionality that will improve diff performance, particularly on complex diffs. We are changing our diff algorithm from what we call a '3-way' diff to a 2-way 'three-dot' diff, which will show the difference between the tip of a source branch and the commit from which it branched off the destination, as shown below. This new diff will be implemented on the Pull request page and Branch page in the coming weeks.

We are happy to announce that Bitbucket Pipelines now supports self-hosted runners on Windows. You can create a self-hosted runner and run it on your Windows infrastructure to run builds with the.Net framework. Since you're using your own runner, you won’t be charged for any Bitbucket Pipelines build minutes. This self-hosted runner will be non-containerized, allowing your CI/CD step to access the host’s hardware, such as the graphics card or any connected external devices.