Sunsetting Mercurial support in Bitbucket – Bitbucket
Posted by jpluimers on 2020/01/30
February 1st, the start commences of Sunsetting Mercurial support in Bitbucket – Bitbucket [WayBack]. Starting June 1st, only git is supported by Bitbucket, despite them having started with and focused mainly Mercurial at first.
Here are the major dates of the sunset:
- February 1, 2020: users will no longer be able to create new Mercurial repositories
- June 1, 2020: users will not be able to use Mercurial features in Bitbucket or via its API and all Mercurial repositories will be removed.
All current Mercurial functionality in Bitbucket will be available through May 31, 2020.
So by now you should have started migrating from Mercurial to git, probably away from BitBucket.
Reading their community, it looks like an in-place conversion (keeping all issues, comments, wikis, pull-requests, etc) and just replacing the mercurial repository with the converted git repository is impossible.
Given that the user experience on Bitbucket for git repositories is far behind sites like GitHub or GitLab, migrating away after conversion sounds like a very good move.
Conversion used to be hard Moving my BitBucket mercurial repository to git was a lot harder than I hoped for (but moving to GitHub was easy) « The Wiert Corner – irregular stream of stuff
So by now, I am anxious to see if the steps linked from the quote are easier:
We recommend that teams migrate their existing Mercurial repos to Git. There are various Git conversion tools in the market, including [WayBack] hg-fast-export and [WayBack] hg-git mercurial plugin. We are happy to support your migration, and you can find a discussion about available options in [WayBack] our dedicated Community thread.
Edit 20220513: I got notified on this on Twitter while in the midst of the horrible two weeks after my radiation therapy in this thread:
- [Wayback/Archive] Nick Hodges on Twitter: “For the last three hours I have been going toe-to-toe with Python, and Python is kicking my ass.”
- [Wayback/Archive] Craig Chapman on Twitter: “@NickHodges What are you trying to achieve that makes python the right choice?”
- [Wayback/Archive] Nick Hodges on Twitter: “@chapmanworld Converting our hg repository to git. The tool is written in python, and requires Python 2.7, and mercurial to be registered with it. Had Python 3.8, and purging it seems impossible. Just horrible all around.”
- [Wayback/Archive] Jeroen Wiert Pluimers on Twitter: “@NickHodges @chapmanworld Is Bitbucket stopping hg support? If so: when?”
- [Wayback/Archive] Nick Hodges on Twitter: “@jpluimers @chapmanworld It is — as of June 30, 2020
bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket“ - [Wayback/Archive] Jeroen Wiert Pluimers on Twitter: “@NickHodges @chapmanworld Oh crap. I somehow missed that. I guess there is no easy migration to GitHub right?”
- [Wayback/Archive] Nick Hodges on Twitter: “@jpluimers @chapmanworld Not that we’ve found. Plus, we want to migrate to Azure Repos. Migrating to git on local machine seemed easy at first. Not so in reality. Or maybe I’m missing something.”
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a Reply