|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-16404) email-ext regressi... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)
- [JIRA] (JENKINS-16404) email-ext reg... [email protected] (JIRA)

I'm seeing something similar in email-ext 2.24.1 and Jenkins 1.480.1.
My failed and unstable triggers work ok, but it doesn't seem to catch regressions.
The logs does not contain anything useful either...
Could you post any workarounds if you find any?