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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum started work on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 Reopened In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.2053.1557943048064%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum assigned an issue to Devin Nusbaum  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39203  
 
 
  All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Assignee: 
 Devin Nusbaum  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1591.1557943028192%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39203  
 
 
  All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Released As: 
 Pipeline: API 2.34, Pipeline: Basic Steps 2.16, Pipeline: Graph Analysis 1.10, JUnit: 1.28  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1343.1557941225362%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Some changes have recently been released to address this issue. All of the changes require Jenkins 2.138.4 or newer. The main fixes are in Pipeline: API Plugin version 2.34 and Pipeline: Graph Analysis Plugin version 1.10, but in most cases you will need to change your Pipelines to be able to take advantage of the fixes: 
 
If you are currently setting the build result to unstable using currentBuild.result = 'UNSTABLE', you need to update to Pipeline: Basic Steps Plugin version 2.16 and start using the unstable step instead. See the changelog here for details. You may also be interested in the new warnError step. 
 
In case you are curious why we can't make currentBuild.result = 'UNSTABLE' work as-is, the problem is that currentBuild is implemented as a GlobalVariable rather than a regular Pipeline Step, so there is no way to associate the setting of the build result with the current Pipeline stage, especially if a parallel step is being executed. 
  
If the build result is being set to unstable by the junit step from the JUnit Plugin, then update the JUnit Plugin to version 1.28 and the visualization should be fixed. 
If the build result is being set to unstable by the publishIssues or recordIssues steps in the Warnings NG Plugin, then keep an eye on this in-progress PR which will update those steps to use a new API that will fix the visualization. 
If the build result is being set to unstable by a Pipeline step in some other plugin, then file a new issue with the component set to that plugin, and ask the maintainer to start using the new WarningAction API from Pipeline: Basic Steps Plugin version 2.16 wherever they change the build result. 
 In case of problems, the new behavior can be disabled by setting the system property org.jenkinsci.plugins.workflow.pipelinegraphanalysis.StatusAndTiming.DISABLE_WARNING_ACTION_LOOKUP to "true", or by setting the static variable of the same name to true via the Jenkins script console. Note that the Blue Ocean steps view will not yet display the status of individual steps using the new API correctly, keep an eye on this in-progress PR which will fix that issue. Once that PR is merged and released, I plan to mark this issue as closed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

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

2019-05-07 Thread postelmansr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 roel postelmans commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 I'v created a shared library, which contains an API to get the failed stages: https://github.com/roel0/jenkins-util-scripts You can then easily print out that data, or email it , or post it on slack or ...   Example usage: 

 

try {
super_stage("stage1") {
}
super_stage("stage2") {
error "oei"
}
} catch(e) {
}

println "Failed stages: ${get_failed_stages().join(',')}"
 

    
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.19309.1557219184966%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

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

2019-04-15 Thread mlandma...@gmail.com (JIRA)

Title: Message Title

boris ivan commented on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

I can understand the existing logic and methodology makes this difficult to change. But I don't understand why something simple like this couldn't be done as a workaround:

add a new property (doesn't exist today) to each stage object: stageIndependentStatus
when each stage completes, immediately save the value of the independent execution of that stage in stageIndependentStatus
This way, you can let all the existing logic stay as-is regarding stage state, state propagation to other stages, etc – all the things that are difficult to change. The "overall build" would still be marked as it is today. Nothing needs to change. But with that separate property being available per stage, visualizers like blue ocean could implement a configuration: "showStageLegacyStatus" or "showStageIndependentStatus", defined in the options for a pipeline. If the user chooses the latter, visualizers like blue ocean could make their own choice to paint strictly by the stageIndependentStatus.

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.

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

2019-04-15 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Nancy Robertson I think you hit the nail on the head - I am not sure such a facillity exists. If it did - things like this would be possible.   
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-04-15 Thread nancy.robert...@ca.ibm.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nancy Robertson commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 I have a somewhat related question: Is there an API to access the results of the various stages in a pipeline? I have been playing tricks like setting a variable with the name of the current stage when a stage starts and checking its contents in the post for the pipeline to report which stage failed and would like to have a cleaner solution to work with what is already in place...    
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-04-15 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39203  
 
 
  All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-04-15 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Yes it would seem odd from outside - but from inside it kind of makes sense. Plugins mark the whole run as unstable, not a stage. This is a pipeline thing misclassified as blue ocean (other visualisations do the same).  If a build failed then stopped - could just show the "last" stage as unstable only - but if it continues on (which some do by default) then that may be misleading as it may have been an earlier stage that showed it up.   
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-04-15 Thread michael.hartm...@qtronic.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Hartmann commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 From an outside perspective, this is ridiculous. It cannot be that hard to determine and save the result of a single node and color it accordingly.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-04-13 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 this one requires a rewrite of a chunk of pipeline engine - Andrew Bayer is it fair to say that this is part of new generation ?   I don't see this changing for declarative (given all things use "currentBuild." which can't work with this by design) - so I am not sure if this will be done in this form.   
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-03-29 Thread dsvais...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 vaishal shah commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Hi Team, Did anyone found any solution for Declarative Pipeline? Please share details if any solution will be there.   Thanks, Vaishal  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-03-20 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Completely agree with [~borisivan].  To the extent even that I have written Blue Ocean off.  It causes more questions and confusion that it adds value.Instead, I tell my users that GitHub's commit statuses are the point of truth and to that end provide a status for every pipeline stage complete with a URL to (non-Blue Ocean) stage results in the Details link of each GitHub status posted. That this issue has gone on as long as it has with no explanation or status updates on this ticket lately actually makes me wonder what the commitment to Blue Ocean, Pipeline and Jenkins in general is for the future.I see news stories about Jenkins "[reinventing itself|https://www.infoworld.com/article/3366428/jenkins-tries-to-reinvent-itself-as-cloud-native-for-kubernetes.html] and wonder what impact that has on or means for issues like this and others I have opened or commented on with no comments or even a triage in the case of new tickets from any Jenkins developers.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-03-20 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Completely agree with boris ivan.  To the extent even that I have written Blue Ocean off.  It causes more questions and confusion that it adds value. Instead, I tell my users that GitHub's commit statuses are the point of truth and to that end provide a status for every pipeline stage complete with a URL to (non-Blue Ocean) stage results in the Details link of each GitHub status posted. That this issue has gone on as long as it has with no explanation or status updates on this ticket lately actually makes me wonder what the commitment to Blue Ocean, Pipeline and Jenkins in general is for the future. I see news stories about Jenkins "reinventing itself and wonder what impact that has on or means for issues like this and others I have opened or commented on with no comments or even a triage in the case of new tickets from any Jenkins developers.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-03-20 Thread mlandma...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 boris ivan commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 added an attachment 'allYellow.jpg' to illustrate the impact. The various grouping of 12 stages on the right of the pipeline are all test related. Before the pipeline got that far – everything was green, as all those previous stages were successful. And for the 12 test related stages on the right... 2 of them had some failures, the other 10 had no failures. But examining a visualization to get a good understand of what went well and what had issues.. all value is lost, nothing has meaning.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-03-20 Thread mlandma...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 boris ivan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39203  
 
 
  All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
Change By: 
 boris ivan  
 
 
Attachment: 
 allYellow.jpg  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-03-01 Thread mlandma...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 boris ivan edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 I understand that the  job status and  logic associated with the  overall  job status is established throughout Jenkins and that's difficult to adjust. (at least that's what I've heard the problem is, re: 'fixing' this). But in the meantime, can't we just leave that logic alone, and create a new property for the stage object, called 'stage status', that is limited in scope to the execution of that specific stage, and give the user an option to use legacy behavior, or display per-stage-status? The 'overall' job status logic could remain the same.To ignore the entire user base screaming about this about to drive me away, and is so different from the great experience and responsiveness I've had with the Jenkins team over the years.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-03-01 Thread mlandma...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 boris ivan commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 I understand that the job status and logic associated with the job status is established throughout Jenkins and that's difficult to adjust. (at least that's what I've heard the problem is, re: 'fixing' this). But in the meantime, can't we just leave that logic alone, and create a new property for the stage object, called 'stage status', that is limited in scope to the execution of that specific stage, and give the user an option to use legacy behavior, or display per-stage-status? The 'overall' job status logic could remain the same. To ignore the entire user base screaming about this about to drive me away, and is so different from the great experience and responsiveness I've had with the Jenkins team over the years.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-02-28 Thread shchepkin.a...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Shchepkin edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 !image-2019-02-28-17-32-28-257.png!Does the Jenkins team really think this issue is not  unimportant  important ?  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-02-28 Thread shchepkin.a...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Shchepkin commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
  Does the Jenkins team really think this issue is not unimportant?  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-02-28 Thread shchepkin.a...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Shchepkin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39203  
 
 
  All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
Change By: 
 Alexandr Shchepkin  
 
 
Attachment: 
 image-2019-02-28-17-32-28-257.png  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-02-26 Thread yai...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 ‪yair yavneel‬‏ edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 this is necessary to enhance the pipeline status view, to be able to mark each stage status separately, to identify which of them if passed, unstable or failed. It is should not  be  Jenkins's decision to abort the pipeline or not. what if there are independent stages?what if I want to continue and just be aware about test/stage that was failed?I think the status and the abort action should be performed explicitly. for example - stage function that received 3 arguments:1 - stage status (mandatory)2 - Boolean if need to abort (optional - default to continue)3 - message to be print in the stage view window (optional)it is will be very helpful.     
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-02-26 Thread yai...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 ‪yair yavneel‬‏ commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 this is necessary to enhance the pipeline status view, to be able to mark each stage status separately, to identify which of them if passed, unstable or failed.  It is should not Jenkins's decision to abort the pipeline or not.  what if there are independent stages? what if I want to continue and just be aware about test/stage that was failed? I think the status and the abort action should be performed explicitly.  for example - stage function that received 3 arguments: 1 - stage status (mandatory) 2 - Boolean if need to abort (optional - default to continue) 3 - message to be print in the stage view window (optional) it is will be very helpful.     
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-02-20 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 This ticket has added 26 more votes and 20 more watchers in just a hair over a month for a total of 175 and 189, respectively.Could somebody please provide an update on the status of this issue to those 189 watchers please? Is this *+really+* (after all of this time and attention) still just in the {color:#4c9aff}Planned{color} state that the  [Blue Ocean Roadmap|https://jenkins.io/projects/blueocean/roadmap/] indicates?  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-02-20 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 This ticket has added 26 more votes and 20 more watchers in just a hair over a month for a total of 175 and 189, respectively. Could somebody please provide an update on the status of this issue to those 189 watchers please?  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-01-29 Thread jielpe-cbl...@protonmail.com (JIRA)

Title: Message Title

jlpinardon edited a comment on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

Dear all,I want to add here a user experience. The team for which I setup the CI are really in a trouble when they see a totally yellow pipeline. They don't want to make the effort to check each stage one by one to find which is OK and which is not. I can understand that, and .. .well... users or customers are always right, isn't it ? I am afraid that the proposed stage view, with a simple red note will not help. Even if a green note is added for stage with status SUCCESS.In such a situation, have in mind that users don't want to adopt the pipeline. It is a real showstopper show-stopper . And actually, they are currently asking me to come back to something which breaks the pipeline concept._So, I don't know what is the level of complexity, but to have green (or blue) color for stages ended with success, red for NOK ones and yellow for Unstable stages would be nothing else than a must have._ That will really be user friendly and avoid headache for CI guys that must battle against upset users ;).

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

2019-01-29 Thread jielpe-cbl...@protonmail.com (JIRA)

Title: Message Title

jlpinardon edited a comment on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

Dear all,I want to add here a user experience.The team for which I setup the CI are really in a trouble when they see a totally yellow pipeline. They don't want to make the effort to check each stage one by one to find which is OK and which is not.I can understand that, and .. .well... users or customers are always right, isn't it ?I am afraid that the proposed stage view, with a simple red note will not help. Even if a green note is added for stage with status SUCCESS.In such a situation, have in mind that users don't want to adopt the pipeline. It is a real showstopper. And actually, they are asking me to come back to something which breaks the pipeline concept. So _So , I don't know what is the evel level of complexity, but to have green (or blue) color for stages ended with success, red for NOK ones and yellow dor for Unstable stage stages would be nothing else than a must have. _ That will really be user friendly and avoid headache for CI guys that must battle agains against upset users ;).

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

2019-01-16 Thread mlandma...@gmail.com (JIRA)

Title: Message Title

boris ivan commented on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

Was so excited to move our production builds to using the pipeline and blue ocean visualization. With all the stages changing from green to unstable, it's a blocker. Even posting each stage status to slack becomes misleading, in that healthy stages post unstable, and there are instances of unstable stages posting as success, that's a deal breaker right off the bat. Can I suggest a short term workaround? If there was an option in the pipeline: "stageStatus=independent" (or something like that), which worked this way, it would allow us to have control and use blue ocean until it's resolved:

simply allow each stage icon to use the color/state of it's own independent activity
That's it. I'm not sure if that's a flowNode or what, but whatever each icon is in any stage, they all seem to be capable (today) of executing and knowing if that execution was successful or unstable or failure or aborted. If that can simply be retained and displayed for that icon, this works for me. As far as what the overall build status ends up as in this case – if you allow us to set it at the end of the pipeline, we could code that to our own needs, based on the individual statuses per stage.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

2019-01-16 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 This ticket now has 149 votes and 169 watchers, up from 116 and 143 only 4 months ago.  Needless to say that it's affecting a lot of people. It's also very disheartening to see such a critical issue has not made it beyond the same Planned stage on the Blue Ocean Roadmap that it was back at the beginning of September.  It's not even In Progress yet, 4+ months later. Does the Jenkins team really think this issue is that unimportant? I understand that it's complicated, but is that reason enough to not even get started on it?  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2019-01-15 Thread jielpe-cbl...@protonmail.com (JIRA)

Title: Message Title

jlpinardon commented on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

Dear all, I want to add here a user experience. The team for which I setup the CI are really in a trouble when they see a totally yellow pipeline. They don't want to make the effort to check each stage one by one to find which is OK and which is not. I can understand that, and .. .well... users or customers are always right, isn't it ? I am afraid that the proposed stage view, with a simple red note will not help. Even if a green note is added for stage with status SUCCESS. In such a situation, have in mind that users don't want to adopt the pipeline. And actually, they are asking me to come back to something which breaks the pipeline concept. So, I don't know what is the evel of complexity, but to have green (or blue) color for stages ended with success, red for NOK ones and yellow dor Unstable stage would be nothing else than a must have. That will really be user friendly and avoid headache for CI guys that must battle agains users .

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

2018-12-19 Thread stua...@ea.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stuart Rowe commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Georg Henzler, I currently use FlowInterruptedException to achieve the same thing. The added benefit is this exception has a Result field.  I've submitted pipeline-graph-analysis-plugin#PR22 to use the FlowInterruptedException's Result to determine the Stage status rather than using FAILURE (pipeline-graph-analysis-plugin 1.7) or ABORTED (pipeline-graph-analysis-plugin 1.9).  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-11-07 Thread 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.

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

2018-11-07 Thread jenk...@ghenzler.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Georg Henzler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39203  
 
 
  All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
Change By: 
 Georg Henzler  
 
 
Attachment: 
 example-on-how-to-mark-unstable-stages-as-visually-failed-in-stage-overview.png  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

Title: Message Title

Sam Van Oort commented on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

Brian J Murrell Unfortunately, that and the proposed mitigation in https://issues.jenkins-ci.org/browse/JENKINS-53889 are all we've got as viable short-term solutions. It's not a matter of "polluting state" - the data Pipeline needs to figure out which of the stages set the UNSTABLE status simply isn't there, and injecting that into the current system will probably break it completely. Several other engineers and I are working on a comprehensive solution to the things that make this problem hard to solve. We've already had several top Jenkins engineers spend literally months going in circles working on find a solid implementation that solves this specific issue without causing major regressions – the pull requests are out there if you're curious. Unless someone comes up with an unexpectedly clever solution, what's left is waiting for that larger effort to wrap up and then this specific problem will be solved along the way. And that sucks, and we know it's frustrating waiting, but we're doing the best we can to get that to the point of an alpha release.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

2018-10-03 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Sam Van Oort So, no then, your proposal doesn't really help at all, unless there is an angle that I am missing. So to repeat the use-case: 

Say I have 3 parallel stages A, B, and C and A is SUCCESSful and B is UNSTABLE and C is SUCCESSful. Will I be able to determine in stage C that it is SUCCESSful even though stage B was UNSTABLE?
 And to further clarify further, the stages are parallel but A completes before B and B completes before C. I have to be able to determine in C that C was in fact successful. And I really only need to be able to do this because of this whole issue. Because the pass/fail stages cannot be determined any other way by the user, I have to post comments to the PR about which ones actually were UNSTABLE but I cannot even reliably do that if B's state is going to pollute C's state!  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Brian J Murrell currentBuild.currentResult would be entirely unchanged. It has no representation within the Pipeline data model (it directly modifies the build). What this would do is ensure that no stages show up as "unstable" for you. Which gives you what you are asking for.  If you want the ability to keep the UNSTABLE status and figure out which stage actually set it... well, see above, that's way more work than one would reasonably expect (and much riskier too). Plus it requires reworking steps that can generate that status (generally steps that process unit test results, so JUnit and others).   
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-10-03 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 
 
Short term, what we can do is roll back the support for UNSTABLE status. That means you never have to worry about this "bug" because we don't try to signal that a stage somewhere set that status – we simply go back to ignoring it entirely. What do you think?
 Sam Van Oort What is the value of currentBuild.currentResult at various stages with this proposal? Say I have 3 parallel stages A, B, and C and A is SUCCESSful and B is UNSTABLE and C is SUCCESSful. Will I be able to determine in stage C that it is SUCCESSful even though stage B was UNSTABLE? Because that is what currently doesn't happen. Currently, as soon as B hits UNSTABLE, every stage after it is UNSTABLE even if it's not really.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Denis Zakharov Brian J Murrell I've opened JENKINS-53889 which I think would resolve your biggest issue here by making it easy to catch and handle UNSTABLE statuses in declarative.   
 

  
 
 
 
 

 
 
 

 
 
 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.

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

Title: Message Title

Sam Van Oort commented on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

Brian J Murrell [~zaharovdi] Short term, what we can do is roll back the support for UNSTABLE status. That means you never have to worry about this "bug" because we don't try to signal that a stage somewhere set that status – we simply go back to ignoring it entirely. What do you think? In the longer-term, we're building a new Pipeline engine that will replace CPS and provide solutions to a lot of painful issues (sandboxing, lack of an integrated debugger, stability and resource-use problems) and we're planning to address the way we store Step statuses there so that this ceases to be a problem. However I can't give you a firm timeline for that yet. For those who will ask "Why isn't this super easy? Why can't it be done tomorrow?!" – the answer is: "There's nothing actually storing when we set unstable status. And storing that is deceptively complex because statuses can interact and carries a huge risk of regressions." In fact, all the statuses besides success and failure are computed based on a pretty complex and delicate process. Much, much, much more is happening under the surface than users will actually see. Andrew Bayer Would it be viable to add a custom "UNSTABLE OR HIGHER" post condition for the Declarative post conditions? I think that would resolve the part of this that seems to be serious (breaking post behaviors that expect success only).

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

2018-10-03 Thread zakharo...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Denis Zakharov commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Same here. Situation with post actions is very annoying for us. It's broking all logic of pipeline.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-10-02 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Is any progress being made on this issue?I don't want to sound impatient but this is a pretty seriously debilitating issue!  Way beyond even just the graphical display of an entire pipeline of stages and steps looking like it's unstable, this issue completely defeats any and all \{{post { }}} block processing after the first stage failure.  Every stage block from the point of a failed stage on gets processed as unstable, preventing one from doing any kind of finer (than entire pipeline) granulated processing and/or reporting of pipelines.I now personally believe this issue to be higher than *Critical* and believe it to be an outright *Blocker* as it makes much of the usefulness of Pipelines void.  It makes me want to break my pipeline down into separate free-style jobs just so that I can get meaningful reporting and processing of jobs based on whether they are successful, unstable, failed, etc.  A bug serious enough to make one want to abandon Pipelines is by definition a *Blocker* to Pipelines. So, can we get a status update on this?  Is anyone actively working on it or has it been thrown back on the pile?  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-10-02 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Is any progress being made on this issue?I don't want to sound impatient but this is a pretty seriously debilitating issue!  Way beyond even just the graphical display of an entire pipeline of stages and steps looking like it's unstable, this issue completely defeats any and all  \  {{post  \ { }}} block processing after the first stage failure.  Every stage block from the point of a failed stage on gets processed as unstable, preventing one from doing any kind of finer (than entire pipeline) granulated processing and/or reporting of pipelines.I now personally believe this issue to be higher than *Critical* and believe it to be an outright *Blocker* as it makes much of the usefulness of Pipelines void.  It makes me want to break my pipeline down into separate free-style jobs just so that I can get meaningful reporting and processing of jobs based on whether they are successful, unstable, failed, etc.  A bug serious enough to make one  wanting  want  to abandon Pipelines is by definition a *Blocker* to Pipelines.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-10-02 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Is any progress being made on this issue? I don't want to sound impatient but this is a pretty seriously debilitating issue!  Way beyond even just the graphical display of an entire pipeline of stages and steps looking like it's unstable, this issue completely defeats any and all {{post { }}} block processing after the first stage failure.  Every stage block from the point of a failed stage on gets processed as unstable, preventing one from doing any kind of finer (than entire pipeline) granulated processing and/or reporting of pipelines. I now personally believe this issue to be higher than Critical and believe it to be an outright Blocker as it makes much of the usefulness of Pipelines void.  It makes me want to break my pipeline down into separate free-style jobs just so that I can get meaningful reporting and processing of jobs based on whether they are successful, unstable, failed, etc.  A bug serious enough to make one wanting to abandon Pipelines is by definition a Blocker to Pipelines.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-09-14 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title

Jesse Glick commented on JENKINS-39203

Re: All stages show up as UNSTABLE when only one stage should

I do not see any reason to think that this issue is specific to Declarative vs. Scripted. Nor do I think it is necessarily a “huge amount of work”. There is already an API to indicate that a step failed: ErrorAction. This is added implicitly when StepContext.onFailure is called. The overall build status is set to failed (or some other statuses, acc. to FlowInterruptedException) if the FlowEndNode is marked this way, typically because the error was not caught and handled. To set a less severe result, there is a StepContext.setResult API. Unfortunately the implementation in CpsStepContext simply sets an overall build status, which is not useful, and anyway JUnitResultsStepExecution does not call it. There could perhaps be a new action type retroactively implemented by ErrorAction, or somehow related to it, which would be added to a FlowNode when setResult is called and which just defines a getResult method. This would allow JUnitResultsStepExecution to set a per-step UNSTABLE status instead of a build result, at least optionally. (I think this would need to be opt-in for compatibility reasons, unless you declare that setting a step result also makes the build result at least as bad, which may be unwanted.) Then FlowNode.getIconColor would honor the new action, causing Pipeline Steps in the classic UI to show yellow balls where appropriate, and Blue Ocean would need to be patched to do the same.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

2018-09-14 Thread er...@ernstdehaan.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ernst de Haan commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Fully agree with Brian J Murrell. But then should we split this ticket in two? Then… 
 
…one of them (declarative) could be picked up and resolved, 
…while the other one (scripted) could potentially be implemented on a different schedule. 
 An additional benefit could be that when we've got the solution in place for the declarative pipeline, the challenge for implementing the fix for scripted could be reduced, because we already have a guiding implementation in place (the one for declarative).  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-09-14 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 While I can appreciate the desire for a single solution to address both Pipeline styles, if a solution for one of the styles is relatively easy while the other quite complex, let's not let the perfect be the enemy of the good here.  Please.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-09-14 Thread brian.villanu...@nice.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Villanueva commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Georg Henzler - Thanks for the suggestion on using IllegalStateException to turn single stage red. Does this work for the Blue Ocean UI as well? Michael Neale - Are you suggesting that the scope of this issue be narrowed to declarative syntax? I would imagine that many of the voters and watchers of this issue are using scripted pipelines. I know we are, as there are many advanced scenarios that simply are not feasible using declarative syntax.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-09-13 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Indeed yes, it is critical. This has somehow slipped. It was looked at some time ago, but unfortunately is a HUGE amount of work as there is no way in the pipeline engine to track this information (especially not if people are using scripted pipelines, which are still popular, and were included at the time). It is not at all a small job   cc Vivek Pandey Jenn Briden this somehow has slipped off the radar. It was on the old roadmap but don't know the status of it now. Given how old it is, it may be more feasible to do this in a declarative only context now and actually be possible.   
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-09-13 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39203  
 
 
  All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Priority: 
 Major Critical  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-09-13 Thread taylor...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Taylor Patton commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 This critical issue is maddening. It's almost as if we have to separate our pipeline into small components (jobs) like we did with freestyle jobs, for the build status reporting to make sense.  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

2018-09-05 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 I'm failing to understand how this issue is any less than Critical.  It completely invalidates the result of any and every pipeline job run that has even the smallest subset of stage failures.   The problem even propagates outside of Jenkins and Blue Ocean as it leads to other plugins such as the Pipeline Githubnotify Step Plugin incorrectly setting FAILURE status on GitHub PR commit statuses set from stages in the pipeline. This issue leads to developers having to waste time and drive up frustration having to hunt through the stages of their pipeline job runs to figure out which stage actually did fail. Additionally, it's really disheartening to see that this issue is only as far as Planned on the Blue Ocean Roadmap. Surely the 116 (or more) votes and 143 (or more) watchers on this issue demonstrates how important it is for a lot of people.  Other items on the roadmap that are In Progress even, such as JENKINS-44699 don't have anywhere near as many votes and/or watchers. Is there any ETA, no matter how much of guesstimate it is, available as to how long this issue will take to be fixed?  
 

  
 
 
 
 

 
 
 

 
 
 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.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Georg Henzler edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 bq. This build status issue is causing a very large amount of frustration and wastes a lot of developer time trying to dig through logs to deduce failure statuses[~leedega] we have had the same issue. Today we work extensively with [Slack notifications|https://wiki.jenkins.io/display/JENKINS/Slack+Plugin] that contain links to [html reports|https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin] (this is more important than just showing the correctly coloured box anyway, because even with that the developer would still have to check the log file for the actual root cause). In general I think it is great to have a per-pipeline-run build status - this probably shouldn't even be refactored: There are quite some use cases that need that: Notifications to source control if a feature branch can be merged, notifications about "back to normal", just showing a color in the build list in the left panel. That said I think it would be great to have additionally a per stage status, but not only for success/unstable/failed but with a much richer data model - it could e.g. be a list of info, warn and error messages that can be reduced to info/warn/error counts and even more reduced to success/unstable/failed per stage. If that was implemented as stage.info(...), stage.warn(...), stage.error(...) it could under the hood automatically set the per-pipeline-run build status. Plugins could without hassle one by one switch to the new way of setting the build status (while the old way stays intact).All that being said, if for a certain use case it is really important to only "change the color of one box", there is currently one way to achieve it:{code}stage('Stage 1') { echo "green" }try {  stage('Stage 2') { throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 3') { echo "green" }try {  stage('Stage 4') {  throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 5') { echo "green" }{code}Will get you  !overall-success-but-some-stages-marked-as-red.png|thumbnail![~svanoort] As people's grief lies mostly in the UI presentation as it seems (and not in the underlying data model), maybe it could be a very simple change in the pipeline core plugin to show yellow for a  a  predefined exception?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Georg Henzler edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 > bq.  This build status issue is causing a very large amount of frustration and wastes a lot of developer time trying to dig through logs to deduce failure statuses[~leedega] we have had the same issue. Today we work extensively with [Slack notifications|https://wiki.jenkins.io/display/JENKINS/Slack+Plugin] that contain links to [html reports|https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin] (this is more important than just showing the correctly coloured box anyway, because even with that the developer would still have to check the log file for the actual root cause). In general I think it is great to have a per-pipeline-run build status - this probably shouldn't even be refactored: There are quite some use cases that need that: Notifications to source control if a feature branch can be merged, notifications about "back to normal", just showing a color in the build list in the left panel. That said I think it would be great to have additionally a per stage status, but not only for success/unstable/failed but with a much richer data model - it could e.g. be a list of info, warn and error messages that can be reduced to info/warn/error counts and even more reduced to success/unstable/failed per stage. If that was implemented as stage.info(...), stage.warn(...), stage.error(...) it could under the hood automatically set the per-pipeline-run build status. Plugins could without hassle one by one switch to the new way of setting the build status (while the old way stays intact).All that being said, if for a certain use case it is really important to only "change the color of one box", there is currently one way to achieve it:{code}stage('Stage 1') { echo "green" }try {  stage('Stage 2') { throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 3') { echo "green" }try {  stage('Stage 4') {  throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 5') { echo "green" }{code}Will get you  !overall-success-but-some-stages-marked-as-red.png|thumbnail![~svanoort] As people's grief lies mostly in the UI presentation as it seems (and not in the underlying data model), maybe it could be a very simple change in the pipeline core plugin to show yellow for a a predefined exception?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Georg Henzler commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 > This build status issue is causing a very large amount of frustration and wastes a lot of developer time trying to dig through logs to deduce failure statuses Kevin Phillips we have had the same issue. Today we work extensively with Slack notifications that contain links to html reports (this is more important than just showing the correctly coloured box anyway, because even with that the developer would still have to check the log file for the actual root cause).  In general I think it is great to have a per-pipeline-run build status - this probably shouldn't even be refactored: There are quite some use cases that need that: Notifications to source control if a feature branch can be merged, notifications about "back to normal", just showing a color in the build list in the left panel. That said I think it would be great to have additionally a per stage status, but not only for success/unstable/failed but with a much richer data model - it could e.g. be a list of info, warn and error messages that can be reduced to info/warn/error counts and even more reduced to success/unstable/failed per stage. If that was implemented as stage.info(...), stage.warn(...), stage.error(...) it could under the hood automatically set the per-pipeline-run build status. Plugins could without hassle one by one switch to the new way of setting the build status (while the old way stays intact). All that being said, if for a certain use case it is really important to only "change the color of one box", there is currently one way to achieve it: 

 

stage('Stage 1') { echo "green" }
try {
  stage('Stage 2') { throw new IllegalStateException("a failed stage") }
} catch(err) { echo "made the stage only red" }
stage('Stage 3') { echo "green" }
try {
  stage('Stage 4') {  throw new IllegalStateException("a failed stage") }
} catch(err) { echo "made the stage only red" }
stage('Stage 5') { echo "green" }
 

 Will get you   Sam Van Oort As people's grief lies mostly in the UI presentation as it seems (and not in the underlying data model), maybe it could be a very simple change in the pipeline core plugin to show yellow for a a predefined exception?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

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