When clause shouldn't require node to evaluate

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Andrew Bayer
            Reporter:
            Christopher Eck
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: