• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: git-client-plugin
• Labels:

  None
• Environment:

  Git client plugin 1.18.0, Jenkins 1.609.1, Git for Windows 2.5.0

[JENKINS-30045] Git client plugin does not work with new Git for Windows 2.5.0

Will Saxon created issue - 2015-08-20 01:06

Will Saxon made changes - 2015-08-20 01:07

Description

Original: The new [Git for Windows|https://github.com/git-for-windows/git/releases/tag/v2.5.0.windows.1] places the SSH binary in a usr/bin/ subdirectory instead of the bin/ directory used by prior releases of msysgit. This results in an error: {quote}FATAL: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win{quote} The 'official' link takes you to a download for this new Git for Windows, so it's not helpful. A temporary workaround is to create a link to ssh.exe in the $(INSTALLDIR)\bin directory with mklink, e.g.: {quote}mklink "c:\program files\git\bin\ssh.exe" "c:\program files\git\usr\bin\ssh.exe"{quot} Another thing I noticed, not related to the jenkins plugin, is that the new Git for Windows prepends the NetBIOS domain name in a Windows AD environment by default. So existing jobs which don't explicitly set the username will fail, because the default username is now DOMAIN+username.

New: The new [Git for Windows|https://github.com/git-for-windows/git/releases/tag/v2.5.0.windows.1] places the SSH binary in a usr/bin/ subdirectory instead of the bin/ directory used by prior releases of msysgit. This results in an error: {quote}FATAL: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win{quote} The 'official' link takes you to a download for this new Git for Windows, so it's not helpful. A temporary workaround is to create a link to ssh.exe in the $(INSTALLDIR)\bin directory with mklink, e.g.: {quote}mklink "c:\program files\git\bin\ssh.exe" "c:\program files\git\usr\bin\ssh.exe"{quote} Another thing I noticed, not related to the jenkins plugin, is that the new Git for Windows prepends the NetBIOS domain name in a Windows AD environment by default. So existing jobs which don't explicitly set the username will fail, because the default username is now DOMAIN+username.

Mark Waite made changes - 2015-08-20 01:55

Link

New: This issue is duplicated by JENKINS-30032 [ JENKINS-30032 ]

Mark Waite made changes - 2015-08-20 01:56

Assignee

Original: Nicolas De Loof [ ndeloof ]

New: Mark Waite [ markewaite ]

Mark Waite made changes - 2015-08-20 03:40

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Mark Waite made changes - 2015-08-20 13:53

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Tim Bayer made changes - 2015-08-24 23:06

Resolution	Original: Fixed [ 1 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]

Mark Waite made changes - 2015-09-17 11:18

Resolution		New: Cannot Reproduce [ 5 ]
Status	Original: Reopened [ 4 ]	New: Resolved [ 5 ]

Mark Waite made changes - 2015-10-13 17:42

Resolution	Original: Cannot Reproduce [ 5 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

Mark Waite made changes - 2016-01-12 22:02

Assignee

Original: Mark Waite [ markewaite ]

Mark Waite made changes - 2016-02-05 14:53

Assignee

New: Mark Waite [ markewaite ]

Load more newer history items