So we have to either migrate to BlueOcean or to another CI platform. BTW, I just started to play with BlueOcean this month and in general it seems good.
On Wednesday, January 16, 2019 at 3:24:46 PM UTC+2, Brian J. Murrell wrote: > > On Wed, 2019-01-16 at 01:22 -0800, Vitaly Karasik wrote: > > I'm using Jenkins 2.151 with declarative pipeline. This pipeline has > > a few > > stages. > > If one of stages failed, Jenkins classic UI (unlike BlueOcean) shows > > all > > following steps as failed, even they weren't executed at all - see > > attached > > screenshot. > > > > Any ideas how to fix that? > > https://issues.jenkins-ci.org/browse/JENKINS-39203 with 149 votes and > 163 watchers on it. > > Sadly the Blue Ocean Roadmap[1] shows that over two years since the bug > was reported it's not even In Progress yet. It's still only in the > Planned stage. But it's been in that stage since the beginning of > September at least. I suspect a lot longer than that even. > > This seems to me to be a really serious bug. It really almost > completely invalidates the whole concept of the Pipeline job and makes > the Freestyle upstream/downstream job paradigm that it's trying to > replace look a lot more inviting again. > > Anyway, go vote for the ticket. > > Cheers, > b. > > [1] https://jenkins.io/projects/blueocean/roadmap/ > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/90b839f2-434b-48f1-9a0d-92efc79cd1ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
