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.
The Bamboo Automatic Clover Coverage currently has no way to exclude sources from coverage calculation.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs