Thats great to hear, Dallas! We are also making a change so that you can see from the test reporting screen which stage and parallel was responsible for the test result. See JENKINS-46166 <https://issues.jenkins-ci.org/browse/JENKINS-46166>.
Without going into details, the underlying work we need to do for all of these things is highly related. On Fri, Aug 18, 2017 at 12:43 AM Dallas Clement <[email protected]> wrote: > Hi James. This sounds like a dream come true to have status for > individual stages and steps. In my particular situation I need to collect > test results from a lot of bash scripts and somehow tally failure counts > and report them back for each individual test. Will have to think some > more about that and perhaps open a new ticket describing what I need. > Thanks for the help. > > > On Thursday, August 17, 2017 at 1:53:32 AM UTC-5, James Dumay wrote: >> >> 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 a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/3nWDhDOPrE4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/d93a3cf6-1eca-4d67-80cd-16d38eef01f8%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/d93a3cf6-1eca-4d67-80cd-16d38eef01f8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- James Dumay, Director of Product Management. CloudBees, Inc. Skype: jdumaycb Twitter: i386 Meet with me: https://calendly.com/jdumay -- 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/CAErbOvSE-KYAbHyYshZrrV1ZkBknefEEkqc3aHn1t6pDUovb1g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
