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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • job-dsl-plugin
    • None
    • EnvInject 2.1.5
      Job DSL 1.69
      Jenkins 2.107.2

      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.

          [JENKINS-51044] Using non-pipeline directives in pipeline job definitions should result in warning or error

          Aaron D. Marasco added a comment -

          More experimentation seems to imply the directives are always ignored in any pipelineJob, even if I don't set the definition - which also makes sense. These things are supposed to be in the groovy script, so are ignored and the user should be notified.

          Aaron D. Marasco added a comment - More experimentation seems to imply the directives are always ignored in any pipelineJob , even if I don't set the definition - which also makes sense. These things are supposed to be in the groovy script, so are ignored and the user should be notified.

            daspilker Daniel Spilker
            aarondmarasco_vsi Aaron D. Marasco
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: