-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error using with git ssh-agent #171
Comments
Stacktrace for a first run:
|
Stacktrace for subsequent run:
|
I think this is an issue in how JschAgentProxySelector tries to pick it's socket factory. I'll target improving this in the next release. When you tried Pageant, did you set the |
That solved my immediate issue, thanks. Would still be nice to be able to use the ssh-agent that comes with git (and also happily picks up standard openssh keys in the users home/.ssh directory). |
Can confirm in 2.0.0.-rc.1 it no longer throws an error if I have the git ssh agent loaded. |
The error message you were getting (and would see if you had debug logs on), I think indicates some incompatible libraries somewhere. There have been some similar issues in the past ajoberstar/gradle-git#78 and ajoberstar/gradle-git#38. I've never had luck reproducing them, since they tend to be very system-dependent. I'm also not familiar with the specifics of JNA, so not sure exactly what the cause of that would be. |
Using the following code:
(Where directory is a valid git directory)
When ssh-agent is running, I get the following error on the first attempted run:
And then on any other attempts (until I reset the gradle daemon):
It works fine without ssh-agent running - but having to reenter my sshkey password for every repo we're updating from is highly annoying (currently pulling from 12 different repos).
The ssh-agent is the default one that comes with git 2.12.2.windows.2
As per a suggestion I found elsewhere I've also tried installing putty-pageant, without any change in behaviour.
[Edit] Version of grgit is 1.9.2
The text was updated successfully, but these errors were encountered: