How to reconfigure Bamboo agent home after upgrade

[Serge Dukic]

Hi,

We've got a central Bamboo server running six local agents as well as several physical machines running three remote agents each.

We've recently upgraded to Bamboo 4.4.1 and as a result of the upgrade, the build agents have been upgraded and reconfigured. One of the reconfigurations seems to have been that the working directory for the agents is no longer pulled from the "bamboo-agent.cfg.xml" file.

The consequence of this for us is that all of our agents now have their own working directory (previously all agents on a particular machine would share a working directory). This has resulted in a massive increase in the amount of disk space required for our build agents.

How can the agents be reconfigured to use a shared working directory again?

[Serge Dukic · Accepted solution]

After talking with Atlassian support, the solution was to disable Bamboo's Concurrent Build feature. This feature requires that each agent have a seperate directory, as it means that the same build could be run simultaneously on different agents, resulting in issues around duplicate files etc...

Fix was to turn off the Concurrent build feature, which resulted in all of the local agents again using the same working directory.

[Przemek Bruski]

Do you mean the local agents? If you disable concurrent builds, they should still use the same working directory.

[Serge Dukic]

Not just local agents, includes all agents running on the same machine. For example, if "buildmachine3" has 3 agents on it, they should all have the same working directory on that machine. Local agents should share the same working directory on the host machine as well.

From my understanding disabling concurrent builds, would still mean that each agent was using a seperate directory, though they wouldn't be running the builds at the same time. This would still not resolve the issue with the increase in the amount of disk space used.