Git Caches, Shared Repositories, and Automatic Plan Branches

I've noticed lately; while we have enabled a shared repository for our primary plan that every time a branch is detected it creates a new git cache. With our rather large git repository this means we can have easily 30-40 gigs of the same repository, just with a different branch checked out.

This creates a large amount of repeated data on the server; which either requires branches be removed prior to their intended time for expiry, and what I suspect is a large number of unnecessary caches left behind in the _git-repositories-cache folder; or expanding/migrating the Bamboo system to another location with more disk space which is not an optimal solution either.

Can someone explain to me if shared repositories worth with automatic branching for git, and if so what our setup might have wrong that creates a new repository for every branch? And how to properly clean the caches directory of unnecessary caches?

2 answers

1 accepted

Hi,

I'm not sure if this is still an issue for you or not but the " Administration->Repository Settings" for Git exists for Bamboo version 4.4.3 and newer, if you are using an older version of Bamboo it will only be available for Mercurial. Please visit this article for more information:

https://confluence.atlassian.com/display/BAMKB/Git+cache+removal+in+Bamboo

Hope this helps!

Shared repositories will work with automatic branching for Git and should reduce the amount of caches you have on your system. You can also clear caches from Administration->Repository settings

I've seen that entry for managing caches, but it only lists Mercurial, not Git.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,321 views 0 5
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