Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-19040

Suggested Functionality to Better Manage Repo Size

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      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

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            300fb2c7cab6 rickyhaggett
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: