Quantcast

[JIRA] (JENKINS-14525) 'fixed' trigger does not fire when there are no scm changes

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14525) 'fixed' trigger does not fire when there are no scm changes

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Slide-O-Mix
Components: email-ext
Created: 23/Jul/12 8:03 AM
Description:

I have a job that repeatedly builds on jenkins. When there are sporadic failures, I get the failure triggered emails, but the fixed trigger does not fire when the build goes ok the next time.

However, the tooltip on the job config page says "An email will be sent when the build status changes from "Failure" or "Unstable" to "Successful"".

Project: Jenkins
Priority: Minor Minor
Reporter: Mark S.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14525) 'fixed' trigger does not fire when there are no scm changes

JIRA noreply@jenkins-ci.org
Slide-O-Mix commented on Bug JENKINS-14525

Please attach a build log and config.xml for the job.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14525) 'fixed' trigger does not fire when there are no scm changes

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Slide-O-Mix closed Bug JENKINS-14525 as Incomplete

Missing information from submitter.

Change By: Slide-O-Mix (03/Oct/12 3:53 PM)
Status: Open Closed
Resolution: Incomplete
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...