Hi Atlassian team, @Ben
We would like to request your Support Team's help, since we are experiencing the same issue related to Garbage Collector not running automatically.
We have rewritten our Git history and reduced its size. However when pushing to remote, the size hasn't changed yet.
Could you run garbage collection and recalculate the repo size on your end?
Please can you inform us what can we do in order to speed up the GC operation?
Shall you need further information in order to identify the proper repositories, please don't hesistate to contact me directly.
Awaiting your kind reply.
Cheers
MS
Welcome to the community!
Please contact support via Atlassian Support portal. If it is inaccessible for you due to your subscription plan, please let me know so I can notify Atlassian team here.
Yes, I confirm that we are currently unable to contact Support via the Atlassian portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, there is no method for speeding up the automated gc process. GC will execute automatically only once a large garbage threshold is met.
Your largest repo was only 178MB, I executed a manual gc and this reduced it down to 4MB. Your workspace is now ~830MB so will no longer encounter size limit issues.
The size of your workspace can mostly be attributed to its large number of repositories. To prevent this from occurring in future - I would suggest deleting any unused repositories and configuring GIT LFS tracking on frequently used repositories for certain file extensions to prevent any unexpected bloat.
Alternatively, you can sign up for a paid plan - which gives a host of benefits such as dedicated support with no workspace size limitations:
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ben
Thank you for your swift reply. We appreciated your help.
We would ask kindly to run the GC manually only once more, please, also on the repository:
g**_viv*******pagne
which is currently the second largest repo we got (~92.6 MB), as we have cleaned up some files in that and therefore to reduce down the whole workspace.
Please let us know.
MS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's been reduced from 92.6MB > 845KB.
Please let me know if you require any further assistance.
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.