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

When clause shouldn't require node to evaluate

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • pipeline-model-definition-plugin
    • None
    • Jenkins:2.61, pipeline-model-definition: 1.1.4
    • Pipeline - December

    Description

      In previous versions of Jenkins Pipeline, each stage's "where" clause would evaluate quickly, not requiring an allocated node to see if its stage needed to be run.  Suddenly, we see Jenkins  allocating the stage's node to evaluate the "where" clause for each stage.  Allocating nodes for us is fairly expensive and we want to avoid this if the where clause stipulates the stage won't run.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-66796 Matrix command in Declarative Pipeline does not filter nodes correctly.

          • Blocker - Blocks development and/or testing work, production could not run.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-46693 When condition requires executor allocation

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

          Web Link PR #232

          Activity

            People

              abayer Andrew Bayer
              chrisleck Christopher Eck
              Votes:
              10 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: