Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35648

Aborting thread doing git operation leaves repository in unclean state

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: git-client-plugin
    • Labels:
      None
    • Environment:
      Jenkins v2.8
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            kbaltrinic Kenneth Baltrinic added a comment -

            JENKINS-37037 seems to be a related issue.

            Show
            kbaltrinic Kenneth Baltrinic added a comment - JENKINS-37037 seems to be a related issue.
            Hide
            hossaiy yacoub hossain added a comment -

            Is there a solution to this problem? It's really annoying

            Show
            hossaiy yacoub hossain added a comment - Is there a solution to this problem? It's really annoying
            Hide
            erikpaulmiller Erik Miller added a comment -

            Any update?

            Show
            erikpaulmiller Erik Miller added a comment - Any update?

              People

              • Assignee:
                Unassigned
                Reporter:
                dodoent Nenad Miksa
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: