We are facing an issue with the global workspace root path settings.
To bring more structure into our folder-structure I set the
Java variable to set a common path for all newly created slave machines.
This solution worked well with standard slaves running on our "local" Linux nodes. However, we have also some remote slave nodes e.g. for MacOS builds which require custom workspace root paths.
Running jobs on this slaves failed because the global workspace root setting was injected over the locally provided workspace path per slave.
It seems that this per slave setting is overridden by the global setting no matter what.
This is an undesirable behavior as global settings should have lower priorities over fine granular local settings focusing on a certain context.
Please check this behavior and report back why this design decision was made and/or if this is an unintended bug.