-
Bug
-
Resolution: Unresolved
-
Major
In Declarative pipelines the stages that don't run any steps, either by the 'when' block expression being false or previous stage failing/aborting, report success in pipeline stage view. In Blue Ocean, the stages display correctly because it reads a special tag that is set to denote failure, that behavior should apply to stage view as well.
[JENKINS-41009] [Declarative Pipeline] Stage view displays un-executed stages as success
Chris Carson
created issue -
Chris Carson
made changes -
| Epic Link |
New:
|
Philip Stroh
made changes -
| Attachment | New: decl-pipeline-stage-view-bug.PNG [ 36848 ] |
The attached screenshot shows another example (decl-pipeline-stage-view-bug.PNG). Here the second stage was aborted by a user input. The following stages is displayed as successful. This behaviour is very misleading. It would be great if this issue is fixed soon.
Philip Stroh
added a comment - - edited The attached screenshot shows another example (decl-pipeline-stage-view-bug.PNG). Here the second stage was aborted by a user input. The following stages is displayed as successful. This behaviour is very misleading. It would be great if this issue is fixed soon.
Sam Van Oort
added a comment - philip It will not be fixed any time soon.
abayer This is why we need to not introduce non-back compatible status coding in Declarative.
Sam Van Oort
added a comment - philip It will not be fixed any time soon.
abayer This is why we need to not introduce non-back compatible status coding in Declarative. Sam Van Oort
made changes -
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Sam Van Oort
added a comment - Won't fix because we've broken the status coding model in Declarative – this will be handled by JENKINS-26522 implementation however
Sam Van Oort
added a comment - Won't fix because we've broken the status coding model in Declarative – this will be handled by JENKINS-26522 implementation however Philip Stroh
added a comment - svanoort I understand from your comment that this issue gets fixed if JENKINS-26522 is implemented, correct? I would then suggest to link both tickets to signal that this issue is blocked by JENKINS-26522.
Philip Stroh
added a comment - svanoort I understand from your comment that this issue gets fixed if JENKINS-26522 is implemented, correct? I would then suggest to link both tickets to signal that this issue is blocked by JENKINS-26522 . 
Andreas Røsdal
added a comment - This problem is still present: In declarative pipelines the stage view displays un-executed stages as success.
If the 'when' directive is the documented way to skip stages in declarative pipelines, then the stage view should reflect that.
Andreas Røsdal
added a comment - This problem is still present: In declarative pipelines the stage view displays un-executed stages as success.
If the 'when' directive is the documented way to skip stages in declarative pipelines, then the stage view should reflect that.
https://jenkins.io/doc/book/pipeline/syntax/#when 
And https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/88, though not fixing the visual weirdness, should clarify this a bit. Thanks Andrew for that again