This came from http://stackoverflow.com/q/7891709/398670 which describes a workaround for it with some Groovy, too.
An option like this would be a real plus. It's frustrating to have one offline node block a matrix build completely, and I'd love to be able to make them skippable instead. Yes, that means the ppc64 RPMs won't get built, but ... oh well, I'd rather have the x86_64 ones completed so the test jobs can fire.
The alternative seems to be to use generated template builds instead of matrix builds. So each chain of build tasks is independent, and runs only if the relevant build worker is available. ppc64 test => ppc64 test => ppc64 package => ppc64 packagetest => ppc64 packagepublish, etc. Rather than parameterizing each build. That works, but largely prevents the use of the Jenkins UI instead of a yaml build plugin and scripting.
This came from http://stackoverflow.com/q/7891709/398670 which describes a workaround for it with some Groovy, too.
An option like this would be a real plus. It's frustrating to have one offline node block a matrix build completely, and I'd love to be able to make them skippable instead. Yes, that means the ppc64 RPMs won't get built, but ... oh well, I'd rather have the x86_64 ones completed so the test jobs can fire.
The alternative seems to be to use generated template builds instead of matrix builds. So each chain of build tasks is independent, and runs only if the relevant build worker is available. ppc64 test => ppc64 test => ppc64 package => ppc64 packagetest => ppc64 packagepublish, etc. Rather than parameterizing each build. That works, but largely prevents the use of the Jenkins UI instead of a yaml build plugin and scripting.