-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins 2.86, Git Plugin 3.6.0, Git Client Plugin 2.5.0
Some builds spuriously fail with the following error message:
stderr: fatal: Unable to create 'h:/hudson/pipeline-github/core/.git/index.lock': File exists. Another git process seems to be running in this repository, e.g. an editor opened by 'git commit'. Please make sure all processes are terminated then try again. If it still fails, a git process may have crashed in this repository earlier: remove the file manually to continue.
I think that there are only a few obvious possibilities here:
1. Jenkins is trying to use the same workspace twice at the same time, which would be a bug on Jenkins' part.
2. Some earlier operation crashed, and Jenkins should be automatically deleting the lock for us, because expecting the user to do this isn't really reasonable for a supposedly automated build system.
3. Some user was diddling with the workspace and deserves to have their lock broken, in which case refer to #2.
- duplicates
-
JENKINS-25353 Git operations fail due to "dead", but lingering lock file
- Closed
-
JENKINS-12513 git plugin should automatically remove .git/index.lock if the job is killed
- Open
- is related to
-
JENKINS-35648 Aborting thread doing git operation leaves repository in unclean state
- Closed
-
JENKINS-12513 git plugin should automatically remove .git/index.lock if the job is killed
- Open