-
Improvement
-
Resolution: Fixed
-
Trivial
-
None
-
Seen on Windows 2008R2, running Hudson 1.371. Pretty sure it applies to any OS.
It would be nice if the Combination Filter of a multi-configuration/matrix job could be specified via a parameter, or to have the contents of a parameter inserted into a part of an existing Combination Filter. The typical $PARAM notation could be used.
We have a large matrix of configuration, taking several hours to run. If one configuration fails, it would be nice to go back and test just that configuration. Hudson-5623 (http://issues.jenkins-ci.org/browse/JENKINS-5623) addresses this same issue. But if that particular issue is too difficult to implement, a configuration Combination Filter would work for us.
We could use a separate up-stream job to get the information from the user about which configuration to run again, then pass it to the matrix job as a parameter that could be used in the Combination Filter to directly target that one configuration.
I note that with the 'Groovy Plugi'n installed it is possible to evaluate an expression as a 'System Groovy Script' such as:
// evaluates to the value of the build param 'myParamName', even in a multi-configuration/matrix job
Thread.currentThread()?.executable.buildVariableResolver.resolve("myParamName")
documented here: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+System+Groovy+script