[
https://issues.jenkins-ci.org/browse/JENKINS-14046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oran t updated JENKINS-14046:
-----------------------------
Environment:
Windows 2008 64-bit
Tomcat 6 (runs as a Windows service with a special "build" domain user)
Jenkins 1.461
Git plugin version 1.1.17
Git version 1.7.10-preview20120409
Remote repository is Assembla
The "mydomain\build" user is properly configured with SSH keys (command-line
access works 100%, jenkins works except when it hangs)
was:
Windows 2008 64-bit
Tomcat 6
Jenkins 1.461
Git plugin version 1.1.17
Git version 1.7.10-preview20120409
> git operations occasionally hang in Jenkins on Windows
> ------------------------------------------------------
>
> Key: JENKINS-14046
> URL: https://issues.jenkins-ci.org/browse/JENKINS-14046
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Environment: Windows 2008 64-bit
> Tomcat 6 (runs as a Windows service with a special "build" domain user)
> Jenkins 1.461
> Git plugin version 1.1.17
> Git version 1.7.10-preview20120409
> Remote repository is Assembla
> The "mydomain\build" user is properly configured with SSH keys (command-line
> access works 100%, jenkins works except when it hangs)
> Reporter: Oran t
> Assignee: Nicolas De Loof
> Priority: Critical
> Labels: git, hang, jenkins, windows
>
> See elaborate description, dumps and discussion at:
> http://stackoverflow.com/questions/10732940/git-operations-occasionally-hang-in-jenkins-on-windows
> Basically, there is a Jenkins environment with some jobs based on GIT with
> periodic polling.
> Each of the main GIT operations in the system (periodic polling, the pull at
> the beginning of a job, and the tag push at the end of a job) all sometimes
> hang, causing builds not to happen.
> I suspect that the GIT plugin is holding handles to some GIT internal files,
> and this locks out the GIT command-line program and causes it to hang at the
> beginning of a run.
> This suspicion is based on a different issue I encountered - I could not wipe
> the workspace for one of the jobs because a GIT pack file was locked. It
> turns out that the process locking the file was Tomcat itself and not the GIT
> process as I expected.
--
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
