Repository size reduction is not reflected in Bitbucket

Hi,

I've followed steps in repository size reduction hints, i.e. created a repository mirror, ran BFG to remove big files, GCed and pushed the changes back to bitbucket.

Now I'd like to ask for some help in understanding the results:

  • I don't see any associated commit in repository history, which is probably expected since there was no commit associated with cleanup - just push from the mirror, is that right?
  • Second concern is that repository size keeps reported on the same level though, even though savings should have been around 600M. Is it taking some time to reflect new repository size?
  • Finally, thanks for gathering all those instructions on various topics including repo cleanup - but it would be super helpful if you followed up on validating the results and included also instructions on what should happen with existing clones (seems like they need to be dropped).

Thanks, Andrey

2 answers

Just to add some details:

  • Size reported by Bitbucket 1.7G
  • Size reported from within a fresh clone by count-objects's size-pack: 626645

Hi, I'm having basically the same issue.  Wondering why this question has been ignored?

Thanks,

  • paulr

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

418 views 5 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you