[Declarative Pipeline] Non-executed stages report success

[Chris Carson]

I am trying out the Declarative Pipeline and noticed some odd behavior in reporting. In the current Scripted Pipeline behavior when a stage fails the pipeline stops and reports as failed, however, 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 the following: start stage -> end stage -> reports the stage as success -> ... -> reports the overall build as a failure.

Example:

Is this a design decision and if so can the stages be instead reported as "not executed" instead of "success"?

[Andrew Bayer]

That's actually addressed with Blue Ocean - we mark failed stages with a special tag that Blue Ocean knows to treat as a failure. I think we could probably do the same in stage view - could you possibly open a JIRA for that? Thanks! 

A. 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bd5fa631-5e70-440d-a2e3-6d9dd2e184da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Carson]

https://issues.jenkins-ci.org/browse/JENKINS-41009

Is there a way to access these failure tags from rest api?

On Wednesday, January 4, 2017 at 11:50:10 AM UTC-6, Andrew Bayer wrote:

That's actually addressed with Blue Ocean - we mark failed stages with a special tag that Blue Ocean knows to treat as a failure. I think we could probably do the same in stage view - could you possibly open a JIRA for that? Thanks! 

A. 

On Jan 3, 2017 15:52, "Chris Carson" <chris....@ni.com> wrote:

I am trying out the Declarative Pipeline and noticed some odd behavior in reporting. In the current Scripted Pipeline behavior when a stage fails the pipeline stops and reports as failed, however, 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 the following: start stage -> end stage -> reports the stage as success -> ... -> reports the overall build as a failure.

Example:

Is this a design decision and if so can the stages be instead reported as "not executed" instead of "success"?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

[Andrew Bayer]

That's a good question - I'll look into that.

A.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/07a4a307-73f5-4c72-8d84-535437d5fcea%40googlegroups.com.