Kohsuke Kawaguchi added a comment - 2013-10-08 19:16 Trilead, the SSH implementation we use underneath, does not support SSH agent. So you'll have to specify the passphrase of your private key inside Jenkins. It'd be good to file a separate RFE for SSH agent support in Trilead if you think it's an important enough addition.

Raphaël Barrois added a comment - 2013-10-10 12:31 The issue doesn't come from the use of SSHAgent: even if I remove that config, I still get a failure. Regarding the clone, I'm cloning from a (private) GitHub repository using GitHub SSH Deploy Keys, without a passphrase, added to the "credentials" section of Jenkins. Here is the error with "SSH Agent" disabled: Started by user anonymous Building remotely on kiso3 in workspace /home/jenkins/workspace/blusers Fetching changes from the remote Git repository FATAL: Cannot open session, connection is not authenticated. java.lang.IllegalStateException: Cannot open session, connection is not authenticated. at com.trilead.ssh2.Connection.openSession(Connection.java:1102) at org.jenkinsci.plugins.gitclient.trilead.TrileadSession.exec(TrileadSession.java:24) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:248) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1105) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:342) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang. Thread .run( Thread .java:679)

Nicolas De Loof added a comment - 2013-10-22 13:56 @Kohsuke : we use a fork of trilead that itself is just a fork maitained by svnkit. Trilead.com don't support this package anymore. I guess it would make more sense to use a supported ssh lib. Apache Mina one for sample

Mark Waite added a comment - 2014-02-17 12:19 Could you check to see if this problem still exists in git-client-plugin 1.6.2 and in git-plugin 2.0.1? A number of other authentication issues have been resolved since this bug was reported, and this one may have been resolved as well.

Mark Waite added a comment - 2014-03-14 11:18 Closing this after a month with no response to the request for verification if the problem still exists.