-
Bug
-
Resolution: Duplicate
-
Minor
-
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.
- duplicates
-
-
- Reopened
-
[JENKINS-51044] Using non-pipeline directives in pipeline job definitions should result in warning or error
Aaron D. Marasco
created issue -
Aaron D. Marasco
made changes -
| Summary | Original: Using conflicting pipeline directives should result in error | New: Using non-pipeline directives in pipeline job definitions should result in warning or error |
Daniel Spilker
made changes -
| Link |
New:
This issue duplicates |
Daniel Spilker
made changes -
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Daniel Spilker
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
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.