Operations | Monitoring | ITSM | DevOps | Cloud

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.

One of my teammates calls change management the "eat your vegetables of ITSM." Just like eating veggies is important for getting nutrients and staying healthy, there is good reason to practice change management — the need for coordination between sometimes misaligned teams and regulatory requirements. Of course, we all know getting our greens can be unappetizing. It's not unlike the often bitter process of navigating complex, slow, and bureaucratic change management systems.

We are happy to announce that Bitbucket Pipelines now supports MacOS self-hosted runners. This is currently in beta. 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. This self-hosted runner will be non-containerised allowing your CI/CD step to access the host's hardware, such as the graphics card or any connected external devices.

We are excited to announce that improvements to the Branch page will be available in Bitbucket Cloud in the coming weeks! Comparing two branches can be a critical step before creating a pull request. We recognize that it can be a cumbersome experience to see the Branch page displayed differently than the Pull request page.

Recently, we introduced support for default values in custom pipeline variables. Today, we're happy to announce the ability to make pipeline variables configuration more flexible with predefined values. We added a property to predefine values that can be assigned to a variable. It helps avoid errors, and improves the user experience. Instead of typing a variable value, you can choose it from a dropdown.

Workspace admins can now set the following project-level settings: default reviewers, access keys, branching model, and merge strategies. These project settings can be inherited by all the repositories in the project.

By now, you’re probably assessing your level of exposure — or are in the middle of remediating — the recently disclosed vulnerability known as Log4Shell. We recently introduced a native integration with Snyk, a leading provider of developer security solutions, to help you address zero-day vulnerabilities. Once enabled, Snyk scans your code and its dependencies, and alerts you about security vulnerabilities, including Log4j. All current versions of Log4j 2 up to 2.14.1 are vulnerable.

Bitbucket Pipelines provides a feature that enables you to configure memory in Docker services (learn more on that here). We have related highly voted suggestion where customers would like to configure multiple Docker services, each with different memory configurations. Here’s a working example of how you can set memory limits to multiple Docker services and use the appropriate service depending on the step requirements.

In July and August of this year, I revealed to our community for the first time that Bitbucket Cloud was engaged in a project to migrate to a new platform. As I wrote in July: I am thrilled to announce that, in late August, we officially completed this project and Bitbucket Cloud has been operating in AWS, data center-free for over 2 months. So how does this benefit our customers? This is one of the most technically complex projects we've ever tackled as a team.