Aborting thread doing git operation leaves repository in unclean state

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

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            Nenad Miksa
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: