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.

By popular demand, we are happy to introduce several new strategies for syncing and merging branches in Bitbucket Cloud. Our goal is to provide you the full functionality of rebase and merge within the Bitbucket UI to help you manage your Git history according to your team's preferences. These new options have been among our most highly voted feature requests. In brief, here's what we've added.

In this blog, we walk through Atlassian's cloud security practices and the controls we give you inside Bitbucket to maintain enterprise-grade security, without the overhead of managing it internally. Security is an essential part of Atlassian's offerings. We manage code and data for over 300,000 customers who serve hundreds of millions of users. To secure data at the scale we operate, we invest more in security than most individual organizations can.

As part of our strategy to build for scale, security, and performance, Bitbucket Cloud is continuing to deliver features that help enterprise teams operate at scale to build world-class software. We've made a lot of progress this year with new features across code review and CI/CD. We've added AI functionality, added features to help you scale your CI/CD workflows, and integrated with Forge, our cloud app development platform, to help you build customizations into Bitbucket to meet your specific needs.

Pull requests are a core feature of Bitbucket Cloud, serving as the hub where code contributions are reviewed, discussed, and approved before being merged into the codebase. Initially, developers focused on ensuring that proposed changes were bug-free, adhered to correct code styling, and included appropriate tests. Over time, the role of pull requests has expanded to act as a checkpoint, ensuring that only high-quality and compliant code reaches production.