Bamboo Cloning Repository to Multiple Directories

I have several Bamboo plans setup and I've noticed that every-so-often a build takes a really long time. When I've looked into the long run times it's always due to Bamboo "cloning repository". It seems that Bamboo will randomly clone the repository from the cached folder into some other folder used for the build. Buy why does it not ALWAYS use that folder?

This is a huge pain because our repository is massive and cloning takes a very long time, is a big load on the server, and causes us to run out of disk space because of all the cloned repositories. Is there any way to prevent this?

4 answers

1 accepted

I think I figured it out. Each directory corresponds to a local agent. To reduce the number of repository clones we need to remove the number of local agents.

Hello Chris,

Just out of curiosity - which repository type (Mercurial? Git?) are you using? I'm wondering which one of them may have so slow cloning operation. Would you be so kind to help me figure that out? :)


The repository is a Mercurial repo.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
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,792 views 0 6
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