-
Improvement
-
Resolution: Unresolved
-
Major
-
None
Currently, the multi-configuration job feature has a static list of axes intersections one can exclude from the build. That works well in simpler projects.
However in more complex projects, which nodes to exclude can be dynamic and can be determined based on any number of factors.
The example I have on hand is that some combinations might be applicable to some branches of a project yet not other branches. Another example is that along with the gerrit trigger plugin, it might be that you want to
{in|ex}clude certain combinations depending on the gerrit changeset number.
As you can see, the criteria for include/exclude could be wide ranging. It would be nice if one could execute actual build steps in the parent job that built the include/exclude list for the child jobs to be run on.