|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
We've run into the same problem today (with different stack trace though).
In order to reproduce defect you must have following plugins installed and enabled (on Jenkins 1.502):
Steps to reproduce defect:
1. Create a project that uses git source control
2. Build it once (successfully)
3. Turn on "E-mail Notification" option on the project setup page
4. Make a change in the git repository that project looks into
5. Run the build again (or use "scm polling" build trigger)
Result: all three plugins call each other in an infinite loop until the end of stack.