[ 
https://issues.jenkins-ci.org/browse/JENKINS-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162602#comment-162602
 ] 

Valentin Rentschler commented on JENKINS-11547:
-----------------------------------------------

Any combination of Jenkins/git-plugin where this does not occur?
                
> Jobs trigger continually even though there are no changes due to git 
> repository being "corrupt"
> -----------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-11547
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11547
>             Project: Jenkins
>          Issue Type: Bug
>          Components: git
>    Affects Versions: current
>            Reporter: James Cook
>            Priority: Blocker
>
> There is a problem with the git polling mechanism which is causing all our 
> jobs to kick themselves off continually. This happens at random times and 
> just fixes itself, but is causing us all sorts of problems due to the large 
> number of builds triggered.
> This is an example of the git polling log:
> {noformat} 
> Started on 28-Oct-2011 03:20:22
> Using strategy: Default
> [poll] Last Build : #480
> [poll] Last Built Revision: Revision abcb8a2492b390521e0c720f96f66a88eae09f18 
> (origin/master)
> Workspace has a .git repository, but it appears to be corrupt.
> No Git repository yet, an initial checkout is required
> Done. Took 0.26 sec
> Changes found
> {noformat} 
> This is caused when a "git rev-parse --verify HEAD" fails for some reason, 
> but there is no logging to help in what might have gone wrong. It looks like 
> the try/catch around the [validateRevision 
> line|https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitAPI.java#L115]
>  is too simplistic and the cause of the exception should be considered before 
> returning false.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to