|
||||||||
|
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 |
||||||||
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/groups/opt_out.
Sorry, but I really have no time left for this issue.
Anyway, I confirm that if I reconfigure (delete/save/add/save) the 1st trigger in a job, then everything is OK, and the "failureCount" property is stored in the config.xml
I did not try direct modification of the config.xml, as I wanted to check for serialization of the current version (that seems OK), but that should do the trick as well.
Note that this can be used as a workaround for 2.27.1.
In conclusion, I would say that the upgrade to 2.27.1 did not handle correctly the conversion (rename) of the triggers; it did not add the "failureCount" property to existing triggers that are now extending NthFailureTrigger. Hence, "failureCount" is set to 0, that leads to immediate trigger for successful build.