Oh, and if your use case is covered by an existing ticket, providing us with more context (like I described for new tickets) as a comment would be fantastic.
On Thursday, August 17, 2017 at 4:52:43 PM UTC+10, James Dumay wrote: > > We are working right now on making sure steps, stages, etc having > individual statuses, a method for setting them at a stage/parallel level > instead of for the whole pipeline and to introduce consistent behaviour > for those statuses in the Blue Ocean pipeline visualisation. > > You can check the status for this on the roadmap > <https://jenkins.io/projects/blueocean/roadmap/> "Unstable stages, > parallels and steps" > > The tickets to watch are: > * JENKINS-39203 <https://issues.jenkins-ci.org/browse/JENKINS-39203> will > make all the statuses consistent, remove unstable setting the whole > pipeline to unstable > * JENKINS-45579 <https://issues.jenkins-ci.org/browse/JENKINS-45579> will > allow you to set a stage to "unstable" using a special step (similar to the > error step) > > If you have any other use cases in mind, please open a new ticket > describing your problem. If you can describe your problem with a mock > Jenkinsfile and a drawing of your desired visualization that helps narrow > things down even further :) > > > > On Wednesday, August 16, 2017 at 6:47:03 PM UTC+10, Dallas Clement wrote: >> >> I have setup a declarative Jenkinsfile for my project. I have some post >> conditions defined for success and failure. I would like to be able to >> determine the job status for the previous build within the 'success' block >> so that I can know if this success is a recovery from a previous failure. >> I do understand that the currentBuild.result variable can be set at >> various stages and that the previous build result is available through >> currentBuild.getPreviousBuild()?.getResult(). But this previous build >> result seems to require the setting of currentBuild.result. >> >> At this point, I am more interested in accessing the actual Jenkins job >> status, i.e. whatever it uses to determine whether a job has been a success >> or failure and not rely on currentBuild.result. Is there some other >> variable available for this? >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2fef554c-2990-485b-aeea-00f1ab85ed91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
