|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reliably removing the lock file and not harming some other use model seems complicated and risky. If a custom workspace is involved, there may be multiple git processes operating in the directory. If a typical workspace is involved, there may be build steps running which start a git process and expect the build step to complete before the git process has completed.
What if we removed lock files as part of the optional "clean" step? Would that have resolved the case you detected? Would you have been willing to clean the workspace to remove the lock file?