[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should

[jenk...@ghenzler.de (JIRA)]

Title: Message Title

Georg Henzler commented on JENKINS-39203   Re: All stages show up as UNSTABLE when only one stage should Following Jesse Glick's advice in his comment, I have digged a bit deeper into this issue and found a way to display what stages actually failed that works today without code change (still all stages show up as UNSTABLE, but the ones that have failed are marked as failed): stage('Build') { } for(int i=1; i<=7; i++) { try{ stage('Test Suite '+i) { if(Math.floor(Math.random() * 3) % 3 == 0) { throw new RuntimeException("tests failed, you would use a custom exception type here") } } } catch(/* your custom exception type here */ err) { currentBuild.result = 'UNSTABLE' } } This creates a stage view as follows: This works because the pipeline-stage-view-plugin [1] takes the exception markers into account per stage. I'm sure blue ocean could also easily show this information. [1] https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/47101e971da4d16a08a4a427c3d72f92cec8ff53/ui/src/main/js/view/templates/pipeline-staged.hbs#L100 Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.