Using non-pipeline directives in pipeline job definitions should result in warning or error

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

XMLWordPrintable

      It seems that certain directives within a pipelineJob are totally ignored if using the definition directive to read in an external groovy script. At a minimum, it seems label and steps are, and possibly wrappers. For a new user (like me!) this can be frustrating. If a directive is invalid or ignored, there should be some message sent to the seed job's console (minimum) or the seed job should have result set to unstable/failed.

            Assignee:
            Daniel Spilker
            Reporter:
            Aaron D. Marasco
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: