please clarify why bb server has such value by default. As per Git gc documentation this turns off automatic garbage collection. Obviously, repository should has some housekeeping in place to avoid performance degradation. So several questions arise here:
1) What is the intention around the 0? Why it is 0?
2) What are implications of changing this value to non-zero value?
3) What is the recommended approach to repo housekeeping in bitbucket?
Thanks in advance.
PS i've read the FAQ but the answer there looks a bit vague to me.
Automatic garbage collection is disabled by default because Bitbucket Server manages garbage collection itself. Disabling auto-gc ensures that garbage collection does not interfere with users pushing new commits, or merging of pull requests.
Instead of relying on auto-gc, Bitbucket Server schedules garbage collection to happen asynchronously, which ensures that user operations are not unnecessarily slowed down.
> 2) What are implications of changing this value to non-zero value?
You should not change this value. Changing it can cause user operations to slow down.
> 3) What is the recommended approach to repo housekeeping in bitbucket?
As said, Bitbucket takes care of the repository housekeeping, but doesn't use git's auto-gc to do it.
Hope this clears up things!
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG