Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
I do not want all of my plans to build in one monolithic file system; in other CI tools, I specify the build directory for each job/plan, and spread my builds out across different filers. This also allows a build to use a less expensive 'update' rather than a full checkout from the source repository if it switches from one remote agent to another between builds. How does one do this with Bamboo? I can't find any way to keep it from using one huge directory (per agent, at least) for doing all the builds?
OK; say I want ProjectA and ProjectB to be on separate file systems; how would I create these symlinks? So far, all I see is that each *job* is getting a separate directory directly under the xml_data/build-dir; IE:
It would make much more sense if there were a subdirectory for each project, then the plans and jobs lived in there. Is there such an option that I am missing? Or are you saying I need to create a symbolic link for every single *job* in each project?
Yes, that's what I'm saying - there's no hierarchy, you need to symlink each job separately.
Also, I think this won't work if you do clean builds or there are problems with your checkouts - the symlink will be erased and a new directory put in its place.
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