• git plugin 4.4.2

      Jenkins Version: 2.204.6

      Git Plugin version: 4.4.1

      Git Client Plugin: 3.4.2

      We have upgraded our Jenkins from 2.204.4 to 2.204.6.  We have also upgraded the plugins during the upgrade.

      Our jobs are not able to perform git checkout from master and slave. The jobs are failing with the below exception.

      Jenkins master and slave configuration of git seems to be precise and we haven't changed any configuration. Jobs were working well before the upgrade.

      1)

      3) 

          [JENKINS-63582] Error performing git command

          Jenkins Version: 2.204.6

          Git Plugin version: 4.4.1

          Git Client Plugin: 3.4.2

          markewaite

          We have upgraded our Jenkins from 2.204.4 to 2.204.6.  We have also upgraded the plugins during the upgrade.

          Our jobs are not able to perform git checkout from master and slave. The jobs are failing with the below exception.

          Jenkins master and slave configuration of git seems to be precise and we haven't changed any configuration. Jobs were working well before the upgrade.

          Grace Lumina Athisaya added a comment - Jenkins Version: 2.204.6 Git Plugin version:  4.4.1 Git Client Plugin: 3.4.2 markewaite We have upgraded our Jenkins from 2.204.4 to 2.204.6.  We have also upgraded the plugins during the upgrade. Our jobs are not able to perform git checkout from master and slave. The jobs are failing with the below exception. Jenkins master and slave configuration of git seems to be precise and we haven't changed any configuration. Jobs were working well before the upgrade.

          Mark Waite added a comment - - edited

          Sorry for the surprise on the upgrade. I suspect that you're using an agent specific tool to define the Git tool. If so, then you can work around the problem by disabling the performance enhancements from the global configuration page.

          Alternatively, you can rollback the git plugin 4.4.1 installation and replace it with git plugin 4.3.0

          If you're not using an agent specific tool installer for command line git, please describe your tool configuration in more detail so that we can duplicate the problem.

          Mark Waite added a comment - - edited Sorry for the surprise on the upgrade. I suspect that you're using an agent specific tool to define the Git tool. If so, then you can work around the problem by disabling the performance enhancements from the global configuration page . Alternatively, you can rollback the git plugin 4.4.1 installation and replace it with git plugin 4.3.0 If you're not using an agent specific tool installer for command line git, please describe your tool configuration in more detail so that we can duplicate the problem.

          Mark Waite added a comment -

          fix is in progress in PR-949. We'd love to have additional testing to confirm that the fix handles all the cases where issues are being encountered. I've uploaded a pre-release build as git-4.4.2-rc4027.193b7e5f6521.hpi . If your installation allows it, could you confirm that it resolves the issue you're seeing? If you encounter any problems with that pre-release build, please report them in PR-949.

          Mark Waite added a comment - fix is in progress in PR-949 . We'd love to have additional testing to confirm that the fix handles all the cases where issues are being encountered. I've uploaded a pre-release build as git-4.4.2-rc4027.193b7e5f6521.hpi . If your installation allows it, could you confirm that it resolves the issue you're seeing? If you encounter any problems with that pre-release build, please report them in PR-949 .

          I've just install the hpi and started the failing pipeline. Now it works fine again for me. Great work! Thanx

          Thomas Stecher added a comment - I've just install the hpi and started the failing pipeline. Now it works fine again for me. Great work! Thanx

          Mark Waite added a comment -

          Thanks very much java_junkie! Would love to hear confirmation from others as well.

          Mark Waite added a comment - Thanks very much java_junkie ! Would love to hear confirmation from others as well.

          I have the same problem, but performance enhancements are not enabled.

          On a dummy Jenkins, I created a global git tool using a path to a classic "Hello World" script, then created a freestyle job with Git configured to use this new tool. With git-4.3.0, the job fails as expected, while git-4.4.0 uses the default "git", which succeeds if there is one in current Path.

          On our prod Jenkins, checkout is no longer possible for agents where Git is not available from Path.

           

          I can also confirm the pre-released 4.4.2 fixes the problem. I'll rollback to 4.3.0 for now.

          Nicolas Boussuge added a comment - I have the same problem, but performance enhancements are not enabled. On a dummy Jenkins, I created a global git tool using a path to a classic "Hello World" script, then created a freestyle job with Git configured to use this new tool. With git-4.3.0, the job fails as expected, while git-4.4.0 uses the default "git", which succeeds if there is one in current Path. On our prod Jenkins, checkout is no longer possible for agents where Git is not available from Path.   I can also confirm the pre-released 4.4.2 fixes the problem. I'll rollback to 4.3.0 for now.

          Hi Mark,

          I've just installed the official update and it works fine. Thank's al lot for supplying it!

          Cheers, Tom

          Thomas Stecher added a comment - Hi Mark, I've just installed the official update and it works fine. Thank's al lot for supplying it! Cheers, Tom

            Unassigned Unassigned
            grace_lumina Grace Lumina Athisaya
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: