Bamboo pulls entire directory tree from perforce

We have had this on and off issue where for some reason when we pull our project from perforce with Bamboo, it gets caught up in downloading the entire directory tree from the top-level, instead of just the root of the project we are wanting. We can work around this issue by simply recreating the plan, and then it will work.


If I am wanting to retrieve //MyProd_DOG/Animal/Canine/Dog/...

when it works correctly, we get just the contents of "dog" as our root working area. When it breaks, I will get the entire directory structure "(root)/Animal/Canine/Dog/..." and i can't call my scripts anymore. Like I said, when I recreate the plan, it resolves itself. this is usually triggered when I make adjustments to the plan. The plan will work fine, then I will go in, adjust a task of a job or something, like the description, save it, and then it screws up.

Any ideas?

1 answer


The Bamboo Automatic Clover Coverage currently has no way to exclude sources from coverage calculation.

If you want to exclude coverage you will need to use the Manual Clover option in Bamboo and manually configure Clover for Ant or Clover for Maven to exclude the source files you want.



Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Jan 15, 2019 in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

299 views 5 2
Join discussion

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