We have many plans running on windows virtual machine agents and are facing some space issues - while we managed to solve this problem for the unix agent by sharing the build_dir for all the agents ( using symlinks), I can't figure out a way to make this work for windows agents.
So far, I tried the following :
- specifying the UNC path into the bamboo build config
- mapping the NAS location to a letter (b:\build-dir) and updating the bamboo build config, but the repo fail to check out.
UNC paths are not supported by cmd.exe which Bamboo uses to run external process. You can use mapped network drives but there are some caveats too:
Do you run agents as Windows service? By default, network drive mappings are not available to windows services:
You can use a mapped network drive if you switch to using the Professional edition of the Tanuki service wrapper with bamboo (requires license for each service).
This way you can setup the service wrapper running bamboo Tomcat or agent to map the network drive when the service starts adn unmap when the server is stopped.
We are using this sucecsfully with Bamboo 3.2 and multiple Bamboo agents shring same drive across different VMs.
Hope This Helps, Good Luck!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot