[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite commented on JENKINS-59897 Re: Git Client plugin: No such file or directory Thanks. I don't run with cygwin and I don't test with cygwin. I have enough complexities in the git plugin testing environment that I have not been willing to extend git plugin support to cygwin. Git for Windows is the git officially supported by the git client plugin. Independent of official support, I think it is a very good idea to change the git client plugin to use Unix style '/' in the GIT_ASKPASS. I'm marking this bug report as 'newbie-friendly' so that someone can experiment with writing tests to check the condition and then changing the value of GIT_ASKPASS and SSH_ASKPASS to use Unix style '/' in the path instead of the Windows style '\' . 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.10575.1584807180212%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Andras Kucsma commented on JENKINS-59897 Re: Git Client plugin: No such file or directory Hi Mark! I'm using Windows Server 2019, with git 2.21.0 installed using cygwin. This setup has worked in the past with an older version of git (2.7.0). 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.10572.1584805980174%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite commented on JENKINS-59897 Re: Git Client plugin: No such file or directory Thanks for investigating, Andras Kucsma. Unfortunately, I can't duplicate the results that you are seeing. I'm running Git for Windows 2.25.1.windows.1 from a Windows 10 command prompt. The Windows 10 environment has the latest feature release installed. When I create C:\askpass.bat and set GIT_ASKPASS=C:\askpass.bat git clone https://github.com/MarkEWaite/tasks.git the clone succeeds. If I remove or rename that GIT_ASKPASS file, the clone fails. Can you provide more details on the case where you're seeing the failure? What version of Git for Windows are you running? Are you running something that is not Git for Windows, like possibly git installed from cygwin? 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.10569.1584804780211%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
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://.git This will work (notice the forward slash after C: set GIT_ASKPASS=C:/askpass.bat git clone https://.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)
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title
Andras Kucsma edited a comment 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:{code:java}set GIT_ASKPASS=C:\askpass.batgit clone https://.git{code}This will work (notice the forward slash after C:) : {code:java}set GIT_ASKPASS=C:/askpass.batgit clone https://.git{code} 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
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite edited a comment on JENKINS-59897 Re: Git Client plugin: No such file or directory Are you certain that the user running the Jenkins process on the master computer can write to that temporary directory? The message is an indication that the user can't write to the directory or can't read from the directory. Those temporary files are only used for the duration of a single command line git call which is run by the git client plugin and the git plugin. After each call, they are deleted.The plugins give their best effort to remove those temporary files when they are no longer needed. There should be no need to regenerate temp files if they do not exist. Can you explain why you believe that you need to regenerate those temporary files? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.3386.1572272580163%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite commented on JENKINS-59897 Re: Git Client plugin: No such file or directory Those temporary files are only used for the duration of a single command line git call which is run by the git client plugin and the git plugin. After each call, they are deleted. The plugins give their best effort to remove those temporary files when they are no longer needed. There should be no need to regenerate temp files if they do not exist. Can you explain why you believe that you need to regenerate those temporary files? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.3384.1572272460115%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Stefan Eicher commented on JENKINS-59897 Re: Git Client plugin: No such file or directory Hi, The folder C:\Users\SVCBUI~1\AppData\Local\Temp exists and can be written. The problem was that I ran a file cleanup in windows to free some space and this has deleted the temp file which the job does not find anymore. Therefore I wanted to know if I can somehow force the plugin to regenerate those temp files if they do not exist Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.3361.1572270240122%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title
Mark Waite edited a comment on JENKINS-59897
Re: Git Client plugin: No such file or directory
The plugin assumes that the temporary directory exists and can be written. Double check that {{C:\Users\SVCBUI~1\AppData\Local\Temp}} exists and can be written by the user running the agent (or in this case with {{git ls-remote}}, the user running the master) .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.18394.1571839620109%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite resolved as Not A Defect Jenkins / JENKINS-59897 Git Client plugin: No such file or directory Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.18392.1571839560511%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite commented on JENKINS-59897 Re: Git Client plugin: No such file or directory The plugin assumes that the temporary directory exists and can be written. Double check that C:\Users\SVCBUI~1\AppData\Local\Temp exists and can be written by the user running the agent. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.18390.1571839560470%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59897 Git Client plugin: No such file or directory Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.18388.1571839440192%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Stefan Eicher created an issue Jenkins / JENKINS-59897 Git Client plugin: No such file or directory Issue Type: Bug Assignee: Mark Waite Attachments: image-2019-10-23-08-09-24-085.png Components: git-client-plugin Created: 2019-10-23 06:21 Environment: Git Client plugin: No such file or directory Priority: Minor Reporter: Stefan Eicher Hi, I let Windows cleanup some files includeing the tmp files. Then I hit the following Problem described later. I am aware of: "The Git Client plugin uses GIT_ASKPASS and creates a temporary script to execute when git prompts for credentials. " https://wiki.jenkins.io/display/JENKINS/Git+Client+Plugin. Can I somehow force the plugin to regenerate those temp files like pass485608812120386475.bat? Or do you have a other solution on how to fix this problem on my installation? Regards Stefan Problem : Failed to connect to repository : Command "git.exe ls-remote -h https://Firmware HEAD" returned status code 128: stdout: stderr: error: cannot run C:\Users\SVCBUI~1\AppData\Local\Temp\pass485608812120386475.bat: No such file or directory fatal: could not read Username for 'https://.com': terminal prompts disabled
