Suggested Functionality to Better Manage Repo Size

Issue #19040 closed
RickyH created an issue

Hey folks,

We’re using Mercurial for game development, and we need to be able to check in assets with code - we really, really need them in sync.

We already hand off huge assets like audio + video to Dropbox, where it isn’t so crucial that they stay in sync with code, but we still hit the 2gb limit, about once every 4-6 months.

What we’ve been doing is using the Convert extension, to convert from hg → hg, omitting everything except code, so that we only keep the code history, manually copying everything else over, and pushing the result to a brand new repo, before migrating everyone to it. It’s quite tedious.

What would be far preferable is the ability to set a per directory 'history count', so that we only store 2 previous versions for asset directories. Or to allow us to the history from selected directories in place from the website. Anything but having to migrate to a new repo when we hit the limit.

We love Mercurial - it’s perfect for us for everything except this issue. I guess the alternative would be that we move to git + gitlfs, but we’re not in a good place to do that with our current project.

cheers,

Ricky

Official response

  • Amber Van Hecke staff

    After much consideration, we’ve decided to remove Mercurial support from Bitbucket Cloud and the API. Mercurial support will be officially removed on June 1, 2020.

    The decision to deprecate was not easy as we knew there were customers (like yourselves) who were currently using Mercurial for versioning their code. Ultimately, we concluded that sunsetting Mercurial support will allow us to singularly focus on building the best possible experience for the lions share of the market and our users.

    That said, if any critical Mercurial issues arise over the coming months, please reach out to our support team. Our goal is to continue offering the same Mercurial experience you have today, until June 1, 2020.

    Read on to learn more about what led to this decision, timeline, and migration resource support.

Comments (2)

  1. Amber Van Hecke staff

    After much consideration, we’ve decided to remove Mercurial support from Bitbucket Cloud and the API. Mercurial support will be officially removed on June 1, 2020.

    The decision to deprecate was not easy as we knew there were customers (like yourselves) who were currently using Mercurial for versioning their code. Ultimately, we concluded that sunsetting Mercurial support will allow us to singularly focus on building the best possible experience for the lions share of the market and our users.

    That said, if any critical Mercurial issues arise over the coming months, please reach out to our support team. Our goal is to continue offering the same Mercurial experience you have today, until June 1, 2020.

    Read on to learn more about what led to this decision, timeline, and migration resource support.

  2. Log in to comment