|
||||||||
|
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 mec... [email protected] (JIRA)
- [JIRA] (JENKINS-15803) git pollin... [email protected] (JIRA)
- [JIRA] (JENKINS-15803) git pollin... [email protected] (JIRA)
- [JIRA] (JENKINS-15803) git pollin... [email protected] (JIRA)
- [JIRA] (JENKINS-15803) git pollin... [email protected] (JIRA)
- [JIRA] (JENKINS-15803) git pollin... [email protected] (JIRA)
- [JIRA] (JENKINS-15803) git pollin... [email protected] (JIRA)
- [JIRA] (JENKINS-15803) git pollin... [email protected] (JIRA)

Temporarily change base class of GitException to a checked exception and it all becomes clear. Sorry about the line numbers, I was a few versions behind when I made the patch/issue
git.getHeadRev
buildChooser.getCandidateRevisions
Both throw GitException in compareRemoteRevisionWithImpl
The launchCommandIn GitAPI method throws GitException and is not able to distinguish why git fails (see http://stackoverflow.com/questions/4917871/does-git-return-specific-return-error-codes), unless one resorts to
wicked screen scraping stuff.