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 see when
you would ever want that and how it could be useful.
Does anyone know why this is?
In particular, when using a custom, shared workspace, this means that
the parent job of a matrix can stomp on other jobs that use the same
workspace.
*sigh* not been a good day for matrix jobs and throttle-concurrent :-(
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
