Status: Resolved (View Workflow)
Resolution: Won't Fix
It'd be nice to have some syntactic sugar above parallel that would let us emulate the matrix axes of the Matrix Project type - a step that takes a map of variable/axis names with values as a list of possible values for the given axis, and a block of script to execute, which then generates all the permutations of those axes and runs them in parallel. This wouldn't make any changes to test reporting, FlowNode data, etc - it'd just handle execution.
- depends on
JENKINS-37011 Provide a way to write full-fledged Steps in CPS-transformed Groovy
- is related to
JENKINS-27395 distinguish test reports filed from different parts of workflow
I actually need the opposite here: the parallel part is easy enough*, but the missing test result grouping is a hard blocker for me. With 32 combinations across 3 matrix jobs and a total of around 6000 tests grouping is critical.
jglick I haven't checked this for a while, there still is no test result grouping of parallel steps, right? Is that planned somewhere?
*: actually the execution order of the matrix combinations is bad too: they get scheduled in alphabetical order, but scheduling based on execution time / diagonal across all axes would be much more useful to get test result feedback earlier.
missing test result grouping
Right, that is the hard part:
Use Groovy libraries instead.