# Bitbucket will remove support for mercurial **URL:** \ **Category:** Organisation\ **Created:** [August 20, 2019, 1:45pm UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669 "2019-08-20T13:45:53Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\ **Post date:** [August 20, 2019, 1:45pm UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669/1 "2019-08-20T13:45:53Z")
> **[Sunsetting Mercurial support in Bitbucket - Work Life by Atlassian](https://www.atlassian.com/blog/bitbucket/sunsetting-mercurial-support-in-bitbucket)** > > \[Update Aug 26, 2020\] All hg repos have now been disabled and cannot be accessed. \[Update July 1, 2020\] Today,... We mirror our mercurial repository on [Bitbucket](https://bitbucket.org/tryton/) using a simple script that pull from [hg.tryton.org](http://hg.tryton.org) and push to bitbucket. I do not think we should migrate this mirror to git repository. We already have git mirror on github (the creation of new repository was never automated on Bitbucket). So for me, we could just keep the mirror alive until Bitbucket stops them. Then we will deactivate the mirror script, remove the mirror option from [trydevpi.tryton.org](http://trydevpi.tryton.org). If someone has a proposal to add a new mercurial mirror on a hosting service, we can consider adding it. ---
**Author:** ![sergyo](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/sergyo/32/181_2.png) [@sergyo](https://discuss.tryton.org/u/sergyo)\ **Post date:** [August 28, 2019, 6:21am UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669/2 "2019-08-28T06:21:09Z")
We’ve got [all our repositories in bitbucket](https://bitbucket.org/datalife_sco/) so in a short time we have to take a decision about it. I’m curious to know what the rest of the partners with mercurial bitbucket repositories are going to do. Would be interesting to share our thoughts. FYI our first option is to continue using mercurial in another hosting service or self-hosted server but we have a handicap with Drone CI due to by default doesn’t work with a self-hosted mercurial server(\*) and the only mercurial hosting service included is bitbucket. 😔 > [@ced](#): > > If someone has a proposal to add a new mercurial mirror on a hosting service, we can consider adding it. After we evaluate the market options I can put my two cents in. ---
**Author:** ![resteve](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/resteve/32/823_2.png) [@resteve](https://discuss.tryton.org/u/resteve)\ **Post date:** [August 28, 2019, 8:08am UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669/3 "2019-08-28T08:08:46Z")
> [@sergyo](#): > > I’m curious to know what the rest of the partners with mercurial bitbucket repositories are going to do. At the moment, move to git. ---
**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\ **Post date:** [August 28, 2019, 8:44am UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669/4 "2019-08-28T08:44:53Z")
For those who wants to keep Mercurial. There are some options for hosting listed on [MercurialHosting - Mercurial](https://www.mercurial-scm.org/wiki/MercurialHosting) I think a drone drive for [Kallithea](https://kallithea-scm.org/) should not be difficult to implement. But there is also [Heptapod](https://heptapod.net/) which sounds promising as it adds to GitLab Mercurial support. And GitLab has its own CI. ---
**Author:** ![sergyo](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/sergyo/32/181_2.png) [@sergyo](https://discuss.tryton.org/u/sergyo)\ **Post date:** [August 28, 2019, 10:12am UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669/5 "2019-08-28T10:12:19Z")
> [@resteve](#): > > At the moment, move to git. Indeed with git there are more options. > [@ced](#): > > But there is also [Heptapod](https://heptapod.net/) which sounds promising as it adds to GitLab Mercurial support. And GitLab has its own CI. Interesting, although GitLab server seems to be (or was) heavy and slow. ---
**Author:** ![pokoli](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/pokoli/32/22_2.png) [@pokoli](https://discuss.tryton.org/u/pokoli)\ **Post date:** [August 30, 2019, 6:32am UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669/7 "2019-08-30T06:32:22Z")
> [@sergyo](#): > > although GitLab server seems to be (or was) heavy and slow. IIRC running the gitlab server required at least 4GB of ram but there is a [hosted service that includes a free plan](https://about.gitlab.com/pricing/). We’ve been using gitlab for a while and we are very happy with it. Specially for the integrated CI, which is easy to configure and works like a charm. The only pitty is that uses git instead of mercurial. It has a good api (with a [python wrapper](https://python-gitlab.readthedocs.io/en/stable/)), which can be used to dynamically create repositories. If you combine that with [hg-git](https://hg-git.github.io/) it’s possible to create a migration script that moves all the repositories from bitbucket to gitlab without losing any history. ---
**Author:** ![sergyo](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/sergyo/32/181_2.png) [@sergyo](https://discuss.tryton.org/u/sergyo)\ **Post date:** [March 3, 2020, 10:22pm UTC](https://discuss.tryton.org/t/bitbucket-will-remove-support-for-mercurial/1669/8 "2020-03-03T22:22:50Z")
FYI [we moved](https://gitlab.com/datalifeit) to [gitlab.com](http://gitlab.com).