-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins v2.8
I have a build in which some git checkout needs to be done on every node under parallel block. If parallel has failFast: true, then when one parallel branch fails, it immediately kills other branches. If a branch was killed while git clone or git checkout operation was being in progress, then index.lock or shallow.lock (due to shallow clone) remains on windows slave and next build fails because git repository has remained locked.
- 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-47652 "Another git process seems to be running in this repository" when Jenkins is the only thing using workspaces
- Closed
- relates to
-
JENKINS-37037 When git fetch crash or timeout before the Jenkinsfile execution, the internal multibranch workspace is broken
- Resolved