[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Liam Newman closed an issue as Fixed Bulk closing resolved issues. Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.188994.1520441679000.16111.1571801048124%40Atlassian.JIRA.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jo Rhett commented on JENKINS-49997 Re: Pipeline Declarative post unsuccessful block It would be really awesome if the documentation at https://jenkins.io/doc/book/pipeline/syntax/#post-conditions mentioned which states unsuccessful includes, so that we don't have to search to find this issue 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.188994.1520441679000.9923.1565193660320%40Atlassian.JIRA.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Reinhold Füreder commented on JENKINS-49997 Re: Pipeline Declarative post unsuccessful block Thanks Jose Blas Camacho Taboada and Andrew Bayer: this was very quick! 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Andrew Bayer updated JENKINS-49997 This'll be in 1.3.4. Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Andrew Bayer Status: In Review Resolved Resolution: 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49997 Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Jose Blas Camacho Taboada Status: In Progress Review 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-49997 Change By: Jose Blas Camacho Taboada Status: Open 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Andrew Bayer assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Andrew Bayer Assignee: Johan Selenius Jose Blas Camacho Taboada 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Andrew Bayer assigned an issue to Johan Selenius Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Andrew Bayer Assignee: Andrew Bayer Johan Selenius 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Andrew Bayer commented on JENKINS-49997 Re: Pipeline Declarative post unsuccessful block Yeah, a condition that fires whenever the status is not SUCCESS or null seems reasonable. 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-49997) Pipeline Declarative post unsuccessful block
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-":
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.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Andrew Bayer Issue Type: Bug Improvement 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title
Stephen Connolly created an issue
Jenkins / JENKINS-49997
Pipeline Declarative post unsuccessful block
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-03-07 16:54
Priority:
Minor
Reporter:
Stephen Connolly
In my declarative pipeline I need to repeat the same step in the unstable, failure, and aborted post conditions, e.g.
post {
always {
// do some stuff to collect junit reports
}
success {
// push the tags
}
unstable {
sh "mvn nexus-staging:drop"
}
failure {
sh "mvn nexus-staging:drop"
}
aborted {
sh "mvn nexus-staging:drop"
}
}
This is really crappy having to repeat the exact same tidy-up in three places. What I'd really like is something like:
post {
always {
// do some stuff to collect junit reports
}
success {
// push the tags
}
unsuccessful {
sh "mvn nexus-staging:drop"
}
}
Where the unsuccessful steps would run at the end. The sequence of execution would thus be:
always (first because it might affect the build result)
success (the result cannot get better, so none of the following blocks can turn the result to a success)
