|
||||||||
|
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-15803) git polling mechanism can have build in infinite loop
kristian.rosenv...@gmail.com (JIRA) Mon, 12 Nov 2012 22:27:47 -0800
- [JIRA] (JENKINS-15803) git polling mec... kristian.rosenv...@gmail.com (JIRA)
- [JIRA] (JENKINS-15803) git pollin... kristian.rosenv...@gmail.com (JIRA)
- [JIRA] (JENKINS-15803) git pollin... kristian.rosenv...@gmail.com (JIRA)
- [JIRA] (JENKINS-15803) git pollin... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15803) git pollin... nicolas.del...@gmail.com (JIRA)
- [JIRA] (JENKINS-15803) git pollin... kristian.rosenv...@gmail.com (JIRA)
- [JIRA] (JENKINS-15803) git pollin... kristian.rosenv...@gmail.com (JIRA)
- [JIRA] (JENKINS-15803) git pollin... kristian.rosenv...@gmail.com (JIRA)
https://github.com/jenkinsci/git-plugin/pull/110 wraps any GitException in a runtime exception. Given that it is "impossible" to reliably separate real IOExceptions from configuration/corruption exceptions, this seems like the least evil of the two possible solutions. It should avoid runaway builds and the subsequent email spamming from jenkins.