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

Matrix structure for Declarative Pipeline

    XMLWordPrintable

Details

    • Declarative backlog

    Attachments

      Issue Links

        is duplicated by

        New Feature - A new feature of the product, which has yet to be developed. JENKINS-49662 Ability to create custom stages in parallel blocks in pipeline shared library

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed
        relates to

        New Feature - A new feature of the product, which has yet to be developed. JENKINS-27395 distinguish test reports filed from different parts of workflow

        • Major - Major loss of function.
        • Resolved

        Story - Created by Jira Software - do not edit or delete. Issue type for a user story. JENKINS-41334 Support parallel execution of stages in Declarative

        • Critical - Crashes, loss of data, severe memory leak.
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. JENKINS-56000 Pipeline fails if more than 250 parameters specified

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        New Feature - A new feature of the product, which has yet to be developed. JENKINS-42808 matrix-project support for pipeline jobs

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        New Feature - A new feature of the product, which has yet to be developed. JENKINS-46809 Allow sequential stages inside parallel in Declarative syntax

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed
        links to

        Web Link PR-251

        Activity

          Ascending order - Click to sort in descending order
          View 17 older comments
          simon_lg Simon Larouche-Gagne added a comment -

          +1 on the exclude syntax, it's taking a lot of space.
          Also, can the values field of the axis block be dynamic instead of using a filter parameter?
          I have a use case with axes with a lot of values depending on a parameter, so if I can't act on the matrix values, my only option is to handle it in a when block?
          Also, in most cases, I would rather use a global variable to store my axes values as well, makes it easier to maintain and I could re-use it in another matrix block further down in the script.
          But overall I'm very happy to see a matrix block in declarative pipeline.

          simon_lg Simon Larouche-Gagne added a comment - +1 on the exclude syntax, it's taking a lot of space. Also, can the values field of the axis block be dynamic instead of using a filter parameter? I have a use case with axes with a lot of values depending on a parameter, so if I can't act on the matrix values, my only option is to handle it in a when block? Also, in most cases, I would rather use a global variable to store my axes values as well, makes it easier to maintain and I could re-use it in another matrix block further down in the script. But overall I'm very happy to see a matrix block in declarative pipeline.
          wohali Joan Touzet added a comment -

          One enhancement that might be nice, if possible, is to have the values for an axis name be supported as non-literals. I don't seem to be able to make this work in the current version. Sorry if this isn't the right place, but you were asking for examples above...

           

          Example:

          pipeline {
            environment {
               LOW_ERLANG_VER = '19.3.6.8'
               MID_ERLANG_VER = '20.3.8.24'
               HIGH_ERLANG_VER = '22.2'
          {{  }}}

            stages {
              // ...
              // Other stages that need the values above
              // ...
              stage("Build") {
                matrix {
                  axes {
                    axis {
                      name 'ERLANG_VERSION'
                      values "{$env.LOW_ERLANG_VER}", "${env.MID_ERLANG_VER}", "${env.HIGH_ERLANG_VER}"
          {{          }}}
                  } // axes
                  // ...
                  // do the build with ${ERLANG_VERSION}
                  // ...
                } // matrix
              } // stage
            } // stages
          } // pipeline

          if that makes sense.
          wohali Joan Touzet added a comment - One enhancement that might be nice, if possible, is to have the values for an axis name be supported as non-literals. I don't seem to be able to make this work in the current version. Sorry if this isn't the right place, but you were asking for examples above...   Example: pipeline {   environment {      LOW_ERLANG_VER = '19.3.6.8'      MID_ERLANG_VER = '20.3.8.24'      HIGH_ERLANG_VER = '22.2' {{  }}}   stages {     // ...     // Other stages that need the values above     // ...     stage("Build") {       matrix {         axes {           axis {             name 'ERLANG_VERSION'             values "{$env.LOW_ERLANG_VER}", "${env.MID_ERLANG_VER}", "${env.HIGH_ERLANG_VER}" {{          }}}         } // axes         // ...         // do the build with ${ERLANG_VERSION }         // ...       } // matrix     } // stage   } // stages } // pipeline if that makes sense.
          bitwiseman Liam Newman added a comment -

          wohali
          This totally makes sense. An issue has been opened for it. https://issues.jenkins-ci.org/browse/JENKINS-61047

          bitwiseman Liam Newman added a comment - wohali This totally makes sense. An issue has been opened for it. https://issues.jenkins-ci.org/browse/JENKINS-61047
          kon Kalle Niemitalo added a comment -

          Matrix stages in declarative pipelines have already been implemented and documented: https://www.jenkins.io/doc/book/pipeline/syntax/#declarative-matrix

          Can this issue be closed now, or is something still missing?

          kon Kalle Niemitalo added a comment - Matrix stages in declarative pipelines have already been implemented and documented: https://www.jenkins.io/doc/book/pipeline/syntax/#declarative-matrix Can this issue be closed now, or is something still missing?
          kon Kalle Niemitalo added a comment -

          It seems the last matrix-specific change without a separate Jira issue was in pipeline-model-definition-1.6.0:

          • Add support for matrix to the directive generator (#380)

          So, I'd consider this issue resolved in that version. Please reopen if you disagree.

          kon Kalle Niemitalo added a comment - It seems the last matrix-specific change without a separate Jira issue was in pipeline-model-definition-1.6.0 : Add support for matrix to the directive generator ( #380 ) So, I'd consider this issue resolved in that version. Please reopen if you disagree.

          People

            bitwiseman Liam Newman
            arthurlutz Arthur Lutz
            Votes:
            32 Vote for this issue
            Watchers:
            43 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: