We are excited to introduce a new capability in Bitbucket Pipelines – Step Failure Strategies. This is the first of a set of new features allowing developers to implement more comprehensive logic and control-flow inside their CI/CD pipelines. Failure Strategies are designed to give you explicit control over how your pipeline behaves in the event that an individual step within the pipeline fails.

We are excited to announce the release of ARM builds in the Pipelines cloud runtime. Our release of Linux based ARM runners in cloud allows you to build and deploy software for ARM-based systems with all the benefits of our fully managed CI/CD platform. To use the new cloud ARM runners in your pipeline, make the following modifications to your bitbucket-pipelines.yml file.

We are excited to announce the release of a new capability in Bitbucket Pipelines that will improve your experience diagnosing issues with your pipeline runs, by allowing you to view and access previous runs within the Pipelines UI.

Earlier this year, we took a significant step forward by announcing our new CI/CD runtime, complete with 4x and 8x build sizes as part of our commitment to improve performance. As our users continue to work on increasingly complex projects, the demand for greater computational power has become evident. In response, we are excited to introduce the 16x build size.

Bitbucket Pipelines is excited to announce support for CI/CD third-party secrets – a powerful new feature that enables you to seamlessly retrieve secrets directly from your preferred secret store. This enhancement ensures your workflows remain efficient and secure. Now, you can set up your own integration and customize the utilization of your secrets to suit your needs.

Last year, Bitbucket Cloud introduced custom merge checks. This advanced feature allowed users to go beyond Bitbucket’s built-in branch restrictions and create customized merge criteria for pull requests. Now, we’re expanding this feature to better support large organizations with many repositories. As organizations scale, manually configuring checks at the repository level becomes tedious and prone to inconsistency.

CI/CD workflows are essential for modern software development, enabling scalability, seamless integration, and ease of workflow management. However, migrating these workflows between tools—such as from Jenkins to Bitbucket Pipelines—can feel daunting due to differences in syntax, custom configurations, and repository-specific setups. To address these challenges, we’re thrilled to announce the Jenkins to Bitbucket Pipelines Migration Tool.

We recently spoke with customers who want all the advantages and benefits of being standardized on the Atlassian platform with Bitbucket, with an integrated experience across planning, source control, CI/CD, and beyond, while still being able to take advantage of using GitHub Copilot. In this blog, we’re excited to demonstrate how easy it is to use GitHub Copilot alongside your Bitbucket repos.

Software development requires a comfortable setup to be successful. If a key on your keyboard isn't working, it feels like nothing is working. Your chair, lights, monitor – they all come together to help you be productive. But what's on the screen matters too. If you're looking to improve your focus, reduce eye strain and lift your overall code review experience, Bitbucket Cloud now offers a dark theme option, a long-awaited feature among our most passionate users.

Shadow IT is defined as the use of IT-related hardware or software by an individual without the knowledge of the IT admin. For example, if a user creates a new Bitbucket Cloud workspace within your organization without the knowledge of the organization admin, it can lead to potentially sensitive data being exposed.