Operations | Monitoring | ITSM | DevOps | Cloud

Teams are shipping more code, faster than ever, as they increasingly automate their processes with CI/CD and AI. But high-velocity pull-request workflows and large monorepos, where many PRs are merged continuously, are feeling the pain as they grow: pull requests race to merge before the branch changes again, “green” builds still break due to semantic merge conflicts, and developers are stuck babysitting merges instead of building features.

Bitbucket Pipelines has always been an engine for automating more than just CI/CD, but today, Pipelines takes a first step towards a full agentic automation platform for all the manual, tedious, repetitive work that happens before and after code creation. You’ve probably seen the stat: Development teams spend 84% of their day doing things other than building features. A lot of this work is: This work matters, but it’s not very fun.

Why did your build fail? Ask Rovo, get a clear answer, and even a way to fix it, from anywhere in Bitbucket Pipeline debugging is one of the most common and most painful parts of the development workflow. In our Atlassian research: AI adoption is rising, but friction persists, over 50% of developers reported losing more than 10 hours each week searching for information, onboarding to new code, or toggling between apps.

The Atlassian Rovo Model Context Protocol MCP Server now supports Bitbucket Cloud. AI clients like Claude, ChatGPT, Cursor, and VS Code can now browse repositories, create commits, open pull requests, and check pipeline results, all through the same secure MCP connection that already works with Jira and Confluence.

If you’ve ever run a pipeline, you’ve certainly encountered the following situation: The pipeline fails halfway through, and the cleanup script you needed at the end to tear down test infrastructure or archive the logs never gets to run. Until now, there was no built-in way in Bitbucket Pipelines to guarantee that a step always executes at the end of your pipeline, regardless of what happened before it. Today, we’re fixing that.

In December 2025, we announced our intention to introduce pricing for self-hosted runners so we could provide stronger support and keep investing in new features and ongoing improvements. You’ve told us that having a free option is important. As a result, we’re introducing a new operating model that lets you continue using self‑hosted runners for free with the option to upgrade to a paid premium runners tier as your needs grow.

Continuous delivery is only as good as your ability to understand what’s happening inside your pipelines. When a build is slow, flaky, or burning through capacity, you need more than a green/red status and a wall of logs — you need traces. Bitbucket Pipelines now exposes pipeline execution as OpenTelemetry (OTel) traces via webhook events. This lets you stream detailed pipeline spans into your own observability stack and correlate them with the rest of your system. This post walks through.

If you’ve ever watched a pull request sit for hours because of a flaky test, you know how quickly test suites can turn from safety net into bottleneck. As teams grow, test suites tend to grow even faster because every new feature, bug fix, and regression adds more tests, while old or redundant tests are rarely cleaned up, so over time you end up running far more tests than are strictly needed for reliable feedback.

Last month we shared that a new navigation system is coming to Bitbucket, and we know many of you have been eager to see what it looks like. Today, we’re happy to share that the new navigation is available for to all Bitbucket users. This article covers what’s changing in Bitbucket, when it’s happening, and how you can share feedback with us.

Every year is a big year for Bitbucket, but in 2025, we delivered transformative changes that cap off years of work to make Bitbucket Cloud the secure, scalable, cloud-first standard for large engineering teams around the world. Today, 15M developers build on Bitbucket, including all of Atlassian’s 10,000-strong engineering organization, and Bitbucket Pipelines runs more than 1 billion build minutes per month.