"Another git process seems to be running in this repository" when Jenkins is the only thing using workspaces

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            trejkaz
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: