|
||||||||
|
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-15440) Emailing users at t... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)
- [JIRA] (JENKINS-15440) Emailing users... [email protected] (JIRA)

This just completely killed our server, because this also seems to be triggered by requests to //job/JOBNAME/api/json
I have to figure out where these request come from, but generally I think that this resolving 'feature' is after all a very bad idea.
I'd really like to remove it altogether as I cannot really think of any scenario where this would have been actually useful (given the legacy state of the previously used hard-coded svn repositories)