On Mon, Dec 8, 2014 at 6:36 AM, Tomas Westling
<
tomas.w...@sonymobile.com> wrote:
> I haven't really gotten the Matrix part of our jobs working though.
>
> The way I have tried to get a matrix project working as a workflow is
> through nested for loops
> and using the parallel step.
This demo
https://github.com/jenkinsci/parallel-test-executor-plugin/blob/3cab169421793c322d2a37bb24f48f7ec2fe31dd/demo/JENKINS_HOME/jobs/flow/config.xml
shows how you can launch a bunch of things in parallel on different
slaves (though for a somewhat different purpose).
> Is this the best way to emulate a Matrix project
I think so. The obvious thing which is missing is any tabular
visualization of the results. In other words, you can make your flow
set up any axes you like and build any combinations you like, but
Jenkins will be ignorant of the meaning of any of this, so it cannot
display history per combination, or a graphical overview of the status
of all combinations in a given build. This is one feature CloudBees
has considered as an Enterprise extension, though there are aspects
that might require special integration APIs that could only make sense
in OSS. I have not had time yet to think about the implications in
detail.