My understanding, is that Jenkins prevents multiple builds in the same workspace. So, we can be sure, that if new build is triggered, no other git processes should access the workspace, and .git repository as well. And I believe, that no other users are interacting git at Jenkins slave.

My suggestion is to unlock the git repository (removing .git/git.lock) file before checkout.

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to