[JIRA] (JENKINS-41060) post/changed should make it easy to restrict on the new/previous status

batmat@batmat.net (JIRA)

unread,

Jan 13, 2017, 6:03:01 AM1/13/17

to jenkinsc...@googlegroups.com

Baptiste Mathus updated an issue

Jenkins /

JENKINS-41060

post/changed should make it easy to restrict on the new/previous status

Change By:	Baptiste Mathus
Summary:	post/changed should make it easy to restrict on the new/ previous status

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

batmat@batmat.net (JIRA)

unread,

Jan 16, 2017, 4:18:02 AM1/16/17

to jenkinsc...@googlegroups.com

Baptiste Mathus commented on

JENKINS-41060

Re: post/changed should make it easy to restrict on the new/previous status

Just checked, and it's wee a bit more convoluted. As I forgot, currentBuild.result is only set on FAILURE, hence it is actually:

 
                                                                post {
    changed {
        script {
            if (currentBuild.result == null) {
                mail to: NOTIFICATION_TARGET, subject: "BACK TO SUCCESS: ${currentBuild.fullDisplayName}", body: "Yay! $BUILD_URL"
            }
        }
    }
}
 
                                                            

Add Comment

andrew.bayer@gmail.com (JIRA)

unread,

Feb 26, 2018, 11:40:02 AM2/26/18

to jenkinsc...@googlegroups.com

Andrew Bayer started work on

JENKINS-41060

Change By:	Andrew Bayer
Status:	Open In Progress

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

andrew.bayer@gmail.com (JIRA)

unread,

Feb 26, 2018, 11:40:03 AM2/26/18

to jenkinsc...@googlegroups.com

Andrew Bayer updated

JENKINS-41060

Jenkins /

JENKINS-41060

post/changed should make it easy to restrict on the new/previous status

Change By:	Andrew Bayer
Status:	In Progress Review

Add Comment

andrew.bayer@gmail.com (JIRA)

unread,

Feb 26, 2018, 11:43:02 AM2/26/18

to jenkinsc...@googlegroups.com

Andrew Bayer commented on

JENKINS-41060

Re: post/changed should make it easy to restrict on the new/previous status

PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/248 to add new fixed and regression post conditions. Not as general purpose as what you originally proposed but a lot better fit with the syntax and parsing. =)

Add Comment

andrew.bayer@gmail.com (JIRA)

unread,

Mar 12, 2018, 3:06:02 PM3/12/18

to jenkinsc...@googlegroups.com

Andrew Bayer updated

JENKINS-41060

This'll be in the upcoming Declarative 1.2.8.

Jenkins /

JENKINS-41060

post/changed should make it easy to restrict on the new/previous status

Change By:	Andrew Bayer
Status:	In Review Resolved
Resolution:	Fixed

Add Comment

scm_issue_link@java.net (JIRA)

unread,

Mar 12, 2018, 3:06:03 PM3/12/18

to jenkinsc...@googlegroups.com

SCM/JIRA link daemon commented on

JENKINS-41060

Re: post/changed should make it easy to restrict on the new/previous status

Code changed in jenkins
User: Andrew Bayer
Path:
pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Fixed.groovy
pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Regression.groovy
pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Messages.properties
pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BuildConditionResponderTest.java
pipeline-model-definition/src/test/resources/postOnChangeChanged.groovy
pipeline-model-definition/src/test/resources/postOnChangeFailed.groovy
http://jenkins-ci.org/commit/pipeline-model-definition-plugin/3f433c84f146589c0f10c9529243ac61ec508635
Log:
[FIXED JENKINS-41060] Add new fixed/regression post conditions