[JIRA] (JENKINS-41715) Git credentials selection + git ls-remote test of config is wonky
Title: Message Title robert mundkowsky commented on JENKINS-41715 Re: Git credentials selection + git ls-remote test of config is wonky I have a very similar problem. If I use a SSH key with a passphrase then I get "Too many authentication failures for git" inconsistently. Some days it works and some days it does not. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
robert mundkowsky commented on JENKINS-25172 GIT_SSH not always used for git fetch which LTS version corrects this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
robert mundkowsky commented on JENKINS-25172 GIT_SSH not always used for git fetch thanks! I just tried Jenkins 1.591 with Git Plugin 2.2.6 and it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
robert mundkowsky commented on JENKINS-25172 GIT_SSH not always used for git fetch I seem to have a similar problem. The plugin seems to fail to use GIT_SSH when a "Recursively update submodules" is used. So basically, the parent module is checked out correctly then I get the following failure for for submodule checkout. Note I can use hte plugin to directly check the submodule out (hence the crednetials are correct) : /usr/bin/git submodule update --init --recursive FATAL: Command "/usr/bin/git submodule update --init --recursive" returned status code 1: stdout: Initialized empty Git repository in /export/Apps/srater_recognizer.15.1/SRaterHome/SRater/ASR_Files/files/ELTeach/expunct/.git/ ... stderr: Permission denied (publickey). fatal: The remote end hung up unexpectedly Clone of 'ssh://git@xxx:7999/foo/bar.git' into submodule path 'Foo/bar' failed hudson.plugins.git.GitException: Command "/usr/bin/git submodule update --init --recursive" returned status code 1: stdout: Initialized empty Git repository in /somewhere/.git/ stderr: Permission denied (publickey). fatal: The remote end hung up unexpectedly Clone of 'ssh://git@xxx:7999/foo/bar.git' into submodule path 'Foo/bar' failed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
robert mundkowsky commented on JENKINS-25172 GIT_SSH not always used for git fetch I agree, JENKINS-20941 is closer match for the error I am seeing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
robert mundkowsky edited a comment on JENKINS-25172 GIT_SSH not always used for git fetch I agree, JENKINS-20941 is closer match for the error I am seeing. I would note, that I thought they had fixed JENKINS-20941 since there was a Pull Request, but after reading the Pull Request, seems the fix was not complete. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
