[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Jesse Glick commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. JENKINS-36997 in 1.14 does that in this plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Joe George For sure, share it. Ideally the author of this plugin will pull in your changes so we will get it out of the box standard. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
Joe George edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
In the end I just wrote a new plugin to spawn an actual {{ssh-agent.exe}} process. It's loaded by the ssh-agent plugin so no other changes are necessary to pipelines or anything .If you're interested I can share once I clean it up a little.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
Joe George edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
In the end I just wrote a new plugin to spawn an actual {{ssh-agent.exe}} process. It's loaded by the ssh-agent plugin so no other changes are necessary. If you're interested I can share once I clean it up a little.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Joe George commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. In the end I just wrote a new plugin to spawn an actual ssh-agent.exe process. It's loaded by the ssh-agent plugin so no other changes are necessary. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. As far as I can tell, the only way to authenticate properly under Windows is to pass the username/password to an HTTPS url. See http://stackoverflow.com/a/33630506/14731 and JENKINS-28335 for more details. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Joe George commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. I'm going to file a new issue regarding debug1: pubkey_prepare: ssh_get_authentication_socket: Device or resource busy. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Will Saxon commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. FWIW I don't think I ever got this to work on Windows with Git. I haven't really tried since I put in my original comment last year. At the time, I was getting the same 'device or resource busy' error that Joe got. I assumed it was something with how the socket file/handle was being presented; I've seen where e.g. applications have different methods of writing a file for cygwin- vs. msys-based client applications, whereas Windows/winsock may have a 3rd format. I am not sure why this would be needed for the Git plugin, as it already works with SSH Credentials. For some of our other non-plugin git needs I've either stashed an ssh key on the build machine, or it's possible (but messy) to write a groovy script in EnvInject which will use the job's configured git with programmed credentials. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
I could swear I had this working recently (as mentioned above) but now I am getting a slightly different problem from you guys. I had this working in the past, but it now looks like I am getting a different problem from you.1. ssh-agent seems to launch successfully:{code}[ssh-agent] Using credentials cowwoc[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/tomcat-native ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Started.{code}2. But git.exe is not using it:{code}debug1: Authentications that can continue: publickeydebug1: Next authentication method: publickeydebug1: Offering RSA public key: /c/Users/builds/.ssh/id_rsadebug1: Server accepts key: pkalg ssh-rsa blen 535debug1: read_passphrase: can't open /dev/tty: No such device or address{code}(I got the above debugging output by setting system property GIT_SSH_COMMAND="ssh -v" as mentioned at http://stackoverflow.com/a/36038548/14731)*UPDATE*: I think I get it now. "git in a shell" works fine, but "git plugin" is not. This seems to be a known problem . See https : JENKINS-20356 //groups . google.com/forum/#!topic/jenkinsci-users/4yXiBwwthMg At first glance, it seems you can workaround this problem by using an HTTPS URL for "git checkout" (as opposed to ssh). This gets around the "git plugin" bug (it uses the credentials from Jenkins instead of from ssh-agent).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
I could swear I had this working recently (as mentioned above) but now I am getting a slightly different problem from you guys. I had this working in the past, but it now looks like I am getting a different problem from you.1. ssh-agent seems to launch successfully:{code}[ssh-agent] Using credentials cowwoc[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/tomcat-native ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Started.{code}2. But git.exe is not using it:{code}debug1: Authentications that can continue: publickeydebug1: Next authentication method: publickeydebug1: Offering RSA public key: /c/Users/builds/.ssh/id_rsadebug1: Server accepts key: pkalg ssh-rsa blen 535debug1: read_passphrase: can't open /dev/tty: No such device or address{code}(I got the above debugging output by setting system property GIT_SSH_COMMAND="ssh -v" as mentioned at http://stackoverflow.com/a/36038548/14731) *UPDATE*: I think I get it now. "git in a shell" works fine, but "git plugin" is not. This seems to be a known problem: JENKINS-20356.At first glance, it seems you can workaround this problem by using an HTTPS URL for "git checkout" (as opposed to ssh). This gets around the "git plugin" bug (it uses the credentials from Jenkins instead of from ssh-agent).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
I am could swear I had this working recently (as mentioned above) but now having I am getting a similar slightly different problem as Will and Joe reported from you guys. I had this working in the past , which is to say that "git checkout" is ignoring but it now looks like I am getting a different problem from you.1. ssh-agent and failing with seems to launch successfully : {code} [ssh-agent] Using credentials cowwoc[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/tomcat-native ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Started. {code} ERROR 2. But git.exe is not using it : Error cloning remote repo 'origin' stderr {code}debug1 : Permission denied ( Authentications that can continue: publickey ) debug1: Next authentication method: publickeydebug1: Offering RSA public key: /c/Users/builds/ . ssh/id_rsadebug1: Server accepts key: pkalg ssh-rsa blen 535debug1: read_passphrase: can't open /dev/tty: No such device or address {code} How did you guys enable debug output from git? ( I want to figure out whether it's failing due to got the same error you pasted above debugging output by setting system property GIT_SSH_COMMAND="ssh -v" as mentioned at http://stackoverflow . com/a/36038548/14731)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
[~wsaxon] I am now having a similar problem as Will and Joe reported, which is to say that "git checkout" is ignoring ssh-agent and failing with:{code}ERROR: Error cloning remote repo 'origin'stderr: Permission denied (publickey).{code}How did you guys enable debug output from git? I want to figure out whether it's failing due to the same error you pasted.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Will Saxon I am now having a similar problem as Will and Joe reported, which is to say that "git checkout" is ignoring ssh-agent and failing with: ERROR: Error cloning remote repo 'origin' stderr: Permission denied (publickey). How did you guys enable debug output from git? I want to figure out whether it's failing due to the same error you pasted. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Joe George commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Worked for me too. Howerver, I used chocolatey to install tomcat instead. I also see this issue though: debug1: pubkey_prepare: ssh_get_authentication_socket: Device or resource busy Anyone have any ideas? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Will's installation instructions for Windows worked perfectly (hint: Jenkins expects a 32-bit DLL, even on a 64-bit OS). To the author of this plugin, please update the official documentation with these steps! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
