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.
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events