Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36932

Add a "matrix" step to workflow-basic-steps

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Component/s: pipeline
    • Labels:
      None
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            Use Groovy libraries instead.

            Show
            jglick Jesse Glick added a comment - Use Groovy libraries instead.
            Hide
            cobexer Ing. Christoph Obexer added a comment -

            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.

            Jesse Glick 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.

            Show
            cobexer Ing. Christoph Obexer added a comment - 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. Jesse Glick 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.
            Hide
            jglick Jesse Glick added a comment -

            missing test result grouping

            Right, that is the hard part: JENKINS-27395.

            Show
            jglick Jesse Glick added a comment - missing test result grouping Right, that is the hard part: JENKINS-27395 .

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                abayer Andrew Bayer
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: