[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory

[r0maikx...@gmail.com (JIRA)]

Title: Message Title

Andras Kucsma commented on JENKINS-59897   Re: Git Client plugin: No such file or directory I tracked down the source of this bug. It seems to affect newer git versions, from around version 2.19.2. The problem is, that if git doesn't find a forward slash in the askpass executable path, it thinks it has to look for the binary somewhere in the PATH environment variable: See prepare_cmd() here: https://github.com/git/git/blob/98cedd0233e/run-command.c#L429-L439 The "error: cannot run" part is printed here, after prepare_cmd returns -1, and this is the only case when this happens. https://github.com/git/git/blob/98cedd0233e/run-command.c#L749-L753 It is possible to reproduce this issue without the git jenkins plugin as well. From CMD, assume C:\askpass.bat exists: This will result in the same error: set GIT_ASKPASS=C:\askpass.bat git clone https://<some_private_repo>.git This will work (notice the forward slash after C: set GIT_ASKPASS=C:/askpass.bat git clone https://<some_private_repo>.git It seems like this logic was introduced in this commit in git: [https://github.com/git/git/commit/321fd823897#diff-7577a5178f8cdc0f719e580577889f04R401-R415 ]This is arguably a bug in git, but still, a possible workaround would be to change one of the path separators in the temporary path from a '\' to a '/' Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202643.1571811719000.10553.1584788340302%40Atlassian.JIRA.