On 01/02/2013 12:11, cjo wrote:
I think the reason for this is that the matrix jobs are designed to run
several configs and normally the labels indicate the what type of
machine/OS or other requirements the nodes have.
Indeed, and some of my matrix jobs I only want to run on certain types
of server (such as those with a local database server).
And the matrix configuration allows the job to run on different labels
to build on different Environments. i.e. build for windows and Unix 32
and 64 bit.
Yeah, this is the hack I use to work around this, but it means most of
my matrix jobs have a label axis with just one value in it, which causes
a number of problems:
- the rendering of the matrix grid is weird; it has on row and the
"real" axis is rendered as:
<axis_name>=value1, <axis_name>=value2, <axis_name>=value3
...rather than just:
value1 value2 value3
- I have to remember to add that axis in whenever I copy artefacts from
these jobs
- it adds an unneeded dimension of complexity to the job
and also use the tie parent to slave plugin to limit what node that runs
on if that is an issue.
I presume you mean:
https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Tie+Parent+Plugin
...in which case, it doesn't help here.
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.
