[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block

[r.fuere...@xortex.com (JIRA)]

Title: Message Title

Reinhold Füreder commented on JENKINS-49997   Re: Pipeline Declarative post unsuccessful block In the meantime there are also: "cleanup", which is presumably the suggested "finally" ("Always run after all other conditions, regardless of build status") "regression, but this will not be run anymore if it keeps to be unsuccessful ("Run if the current builds status is worse than the previous builds status") However, I was also looking for an "unsuccessful" to be able to notify for broken build (a) independent of "unstable"/"failure"/"aborted" and (b) also keep notifying if it is still broken (so not just on first broken build, which would be supported by "regression") A little bit related sounds JENKINS-53889? An alternative approach that I guess might also be not easy to support could be a let's call it "multi-<something>": post { always { // do some stuff to collect junit reports } success { // push the tags } unstable|failure|aborted { sh "mvn nexus-staging:drop" } }   => So agreeing with Stephen Connolly, maybe the "unsuccessful" might be the easiest to implement and use!? 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.