Multiple build engines
We're trying to run multiple build engines on a single machine, and there doesn't seem to be much info about this yet. I'd like to make sure there aren't any blockers preventing us from going down this road.
1. The page at http://jazz.net/wiki/bin/view/Main/DebuggingTheBuildFarm seems to suggest that multiple build engines on a single machine can fail with build collisions. Is that true for all cases, including different install folders/workspaces, or is this related just to the vendor's build farm?
2. Each build definition and build engine are able to specify ant properties, and there's a "Properties file" field in the build definition's Ant tab to specify where those go. Is there a way to variablize that path? With multiple build engines (each at a different location or using a different workspace) I don't want the properties files to overwrite each other.
1. The page at http://jazz.net/wiki/bin/view/Main/DebuggingTheBuildFarm seems to suggest that multiple build engines on a single machine can fail with build collisions. Is that true for all cases, including different install folders/workspaces, or is this related just to the vendor's build farm?
2. Each build definition and build engine are able to specify ant properties, and there's a "Properties file" field in the build definition's Ant tab to specify where those go. Is there a way to variablize that path? With multiple build engines (each at a different location or using a different workspace) I don't want the properties files to overwrite each other.
One answer
sbates wrote:
This is true only for how our builds work in the jazz build farm. It is
a characteristic of our build scripts (all builds load into the same
working directory, hence only 1 can run at a time on the same
filesystem). We have not taken the time to restructure our builds to
allow for multiple engines running on the same machine.
JohnC
SCM Server
1. The page at
http://jazz.net/wiki/bin/view/Main/DebuggingTheBuildFarm seems to
suggest that multiple build engines on a single machine can fail with
build collisions. Is that true for all cases, including different
install folders/workspaces, or is this related just to the vendor's
build farm?
This is true only for how our builds work in the jazz build farm. It is
a characteristic of our build scripts (all builds load into the same
working directory, hence only 1 can run at a time on the same
filesystem). We have not taken the time to restructure our builds to
allow for multiple engines running on the same machine.
JohnC
SCM Server