Bitbucket

Bitbucket is a hosted repository platform that stores source code and coordinates changes among software teams. Its central objects are repositories, branches, commits, pull requests, and project permissions; the service is available as Bitbucket Cloud and, for organizations requiring self-managed infrastructure, Bitbucket Data Center.¹⁴

The service became notable for supporting two distributed version-control systems: Git and Mercurial. Atlassian retired Mercurial repositories from Bitbucket Cloud on June 1, 2020, after providing migration guidance, while Mercurial itself remains an independent open-source version-control system.²⁶ The historical dual-format design distinguishes Bitbucket from services that have always focused exclusively on Git.

Bitbucket’s main workflow lets contributors create branches, commit locally, push changes, and propose a pull request for review before merging it into a shared branch. Pull requests can display diffs, collect comments, require approvals, and enforce conditions such as successful builds or designated reviewers.

Teams organize repositories into projects and control access through workspace, project, and repository permissions. Git operations can use HTTPS or SSH authentication, while web interfaces and APIs support repository administration and automation. These features make Bitbucket more than a file store: it acts as a coordination layer around distributed version control, linking the technical record of commits with social practices such as review, discussion, and approval.

Bitbucket is closely integrated with Atlassian’s development toolchain, particularly Jira Software and Confluence. A commit or pull request can be associated with a Jira issue, allowing teams to trace work from a planning item through code changes, review, and release activity.¹

Bitbucket Pipelines provides continuous integration and continuous delivery inside Bitbucket Cloud. Pipeline definitions are commonly stored as a YAML file in the repository, where they describe steps such as testing, packaging, security checks, and deployment.³ Bitbucket also supports external build and deployment tools through webhooks, APIs, marketplace integrations, and standard Git connectivity, so organizations are not limited to Atlassian’s own automation services.

Bitbucket’s Mercurial heritage is its most distinctive lesser-known aspect: the platform helped make repository hosting available to teams using an alternative to Git, but that compatibility ended in the Cloud product as Atlassian consolidated development around Git.² Migration therefore involved more than changing a website preference; teams had to convert repository history, update remote URLs, revise automation, and retrain contributors.

Bitbucket Cloud and Bitbucket Data Center are not interchangeable deployment models. Cloud delegates infrastructure operation to Atlassian, whereas Data Center is intended for organizations that need control over hosting, network boundaries, identity integration, or operational policies.⁴ Another subtle distinction is between repository hosting and CI/CD: Pipelines is an integrated option, but a Bitbucket repository can also trigger independent build systems through APIs and webhooks.

Bitbucket Cloud

Atlassian’s hosted Bitbucket offering, accessed as an online service and currently centered on Git repositories.

Bitbucket Data Center

Atlassian’s self-managed deployment option for organizations that operate Bitbucket within their own infrastructure.

Pull request

A proposal to merge changes from one branch into another, typically accompanied by review, discussion, and automated checks.

Bitbucket Pipelines

Bitbucket Cloud’s integrated continuous integration and continuous delivery service, configured through repository files.

Mercurial

An open-source distributed version-control system that Bitbucket historically supported alongside Git.