The Simplest Way to Make Bitbucket Mercurial Work Like It Should

You inherited a repo that runs on Mercurial. It has history older than the cafeteria espresso machine, and everyone’s afraid to touch it. Then you open Bitbucket and realize support for Mercurial ended years ago. Now what?

Bitbucket was once the comfortable home for Mercurial repositories. The two fit together perfectly until Atlassian sunset support in 2020, pushing teams toward Git. Still, Mercurial remains in use for certain internal systems, research projects, and compliance-heavy environments that value determinism and stored changesets. Understanding how Bitbucket Mercurial worked—and what fills that gap today—matters for stability and long-term auditability.

At its core, Mercurial is a distributed version control system like Git but with a stricter view of history. Every commit is immutable. Bitbucket, meanwhile, handled repository hosting, permissions, pull requests, and pipelines. Together, the combo gave you private hosting and granular access rules for Mercurial projects without standing up your own infrastructure.

When Atlassian moved away from Mercurial, it forced organizations to rethink three workflows: identity, access, and migration. First, identity now lives primarily in cloud directory services like Okta and Azure AD, which should map to repository-level permissions just as they did in Bitbucket. Second, access automation—those scripts that cloned or pushed code—must now authenticate securely through APIs, not static credentials. Third, data migration is no longer just hg push. Modern systems must export every commit graph to Git structures, often through filtered conversion tools.

For teams that still need centralized review or build automation with Mercurial, internal mirrors of legacy Bitbucket behavior remain possible. You can wrap Mercurial in CI/CD orchestration, attach it to your identity provider via OAuth or OpenID Connect, and log every operation for compliance. Platforms like hoop.dev turn those access rules into guardrails that enforce identity-aware policy automatically, ensuring even aging repos obey current security baselines.

Quick answer: Bitbucket Mercurial provided hosted repositories, permissions, and collaboration features for the Mercurial VCS. After its retirement, comparable workflows rely on Git-based services or self-hosted Mercurial servers secured through identity-aware proxies.

Benefits of modernizing the Bitbucket Mercurial workflow:

• Unified identity via SSO and short-lived tokens instead of static keys
• Clear audit logs for SOC 2 or ISO 27001 reviews
• Automated access rotation across build agents and deploy bots
• Reduced friction for developers cloning or reviewing code
• Freedom to phase in Git without losing historical context

Developers feel the difference immediately. No more waiting for manual repo approvals or forgotten SSH keys. Everything connects faster, and every commit still tells its story. Teams gain speed and trust at the same time, which is a rare thing in version control.

AI tools now analyze commit graphs for anomalies, pattern overlaps, and merge predictions. Using identity-aware systems ensures those automated assistants never overreach into protected branches or private artifacts. In other words, automation gets smarter without getting reckless.

The lesson is simple: Bitbucket Mercurial may belong to history, but the principles it encouraged—secure collaboration, clean history, and explicit control—still guide modern SCM practices.

See an Environment Agnostic Identity-Aware Proxy in action with hoop.dev. Deploy it, connect your identity provider, and watch it protect your endpoints everywhere—live in minutes.