I'm in a similar situation. What I did is set up two matrix jobs: The
first one runs the decision process for all combinations and writes it
out as JUnit result files. The second matrix job is then only
triggered when the first one didn't go all green.
I.e. green (or blue, if you prefer ;-) for the first job means
"everything's up to date, no need to run the second job".
You would need the Parameterized Trigger plugin to only trigger a
downstream job on certain conditions:
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
There's Matrix reloaded plugin [1], however I'm not sure if this is exactly
what you want. What you described is quite high on my TODO list, but I'm not
able to promis any ETA for such plugin:-(
> Is there a way (or a plugin) to do this? In the event there isn't is
> there a way to set a job to 'No Run' once it has started running?
a work around could be System groovy script - you have access to whole Jenkins
JVM, therefore you can run/stop whatever you want (but this is just a hack not
a proper solution)
[1] https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Reloaded+Plugin
> Cheers,
> Stu