Hi Andy,
On 29/01/2013 17:28, fiberquest wrote:
I thought of two things that might help if you have not done them already:
1) use the 'matrix tie parent' plugin and tie matrix jobs to the master
server (I believe this ensures that a random master node is not chosen)
Thanks, this looks ideal :
I thought of two things that might help if you have not done them already:
1) use the 'matrix tie parent' plugin and tie matrix jobs to the master
server (I believe this ensures that a random master node is not chosen)
2) add '-Dhudson.model.WorkspaceCleanupThread.disabled=true' to
the JENKINS_J
Hi All,
Has anyone else noticed that the parent job of a set of matrix builds
appears to still do anything before the "Build" section in the
configuration?
This means that things like Delete workspace and Source Code Management
happen on the node running the parent job, even though I can't s
