I've made a first patch that works fine with OpenSSH agent. I'm going to try to 
test it with Pageant on Windows, as it seems to be supported. I'll then make a 
pull request if my tests are successful.  

If you want to have a look at my change in the mean time: 
https://github.com/rborer/jenkins/commit/281dd560fdcb6a526deedcb83c9e83e1eff3947b

BTW, I had to use jsch-agent-proxy (https://github.com/ymnk/jsch-agent-proxy) 
as a new dependency as it provides communication with SSH agents (ssh2 library 
build 217 only add interfaces for agent authentication…). I hope it's fine to 
add a new dependency, the jar size increase from 2.5 to 3.9 mb.  

Cheers,
Reynald


On Friday, August 2, 2013 at 18:36 , Reynald Borer wrote:

> Great, thanks for the merge, I guess you've done the hardest part with 
> subversion. I'll see for its inclusion in the CLI.
>  
> Cheers,
> Reynald
>  
>  
> @+,
> Reynald
>  
>  
> On Friday, August 2, 2013 at 10:48 , nicolas de loof wrote:
>  
> > released org.jenkins-ci:trilead-ssh2:build217-jenkins-2
> >  
> >  
> > 2013/8/2 nicolas de loof <[email protected] 
> > (mailto:[email protected])>
> > > Sounds good to me
> > > I'm looking into updating svnkit fork to 1.7.10 and need build217 as 
> > > dependency as well
> > >  
> > > But searching for source code to merge, I notice
> > > http://www.ganymed.ethz.ch/ssh2/ only provide outdated build 210,  
> > > it has a link to http://www.cleondris.ch/ where I only can find build 250 
> > > : http://www.cleondris.ch/opensource/ssh2/, but this one has been 
> > > repackaged as ch.ethz.ssh2
> > > svnkit is using a custom version 
> > > http://svn.svnkit.com/repos/3rdparty/com.trilead.ssh2/tags/1.0.0-build217/
> > >  that uses gradle
> > > so I guess I have to use the later, but not trivial to merge with build 
> > > system changed
> > >  
> > > Le mardi 18 juin 2013 13:13:51 UTC+2, Reynald Borer a écrit :
> > > > Hi,
> > > >  
> > > > I'm reposting this to the dev mailing-list which is probably a more 
> > > > appropriate list.
> > > >  
> > > > Let me know what you think of my proposal.
> > > >  
> > > > Regards,  
> > > > Reynald
> > > >  
> > > >  
> > > >  
> > > > On Fri, Jun 14, 2013 at 5:50 PM, Reynald Borer <[email protected]> 
> > > > wrote:
> > > > > Hi,
> > > > >  
> > > > > I'm probably not the only one interested in having Jenkins CLI being 
> > > > > able to use an existing ssh agent instead of prompting for the key 
> > > > > passphrase at every action. I've had a quick look at the code and 
> > > > > haven't found anything about that.  
> > > > >  
> > > > > Luckily, it seems that the trilead ssh2 library released build 217 
> > > > > with ssh agent support a few days ago (according to 
> > > > > http://svn.svnkit.com/repos/3rdparty/com.trilead.ssh2/trunk/HISTORY.txt).
> > > > >   
> > > > >  
> > > > > So I'm wondering if it would be possible to merge this new feature in 
> > > > > the fork of this library for Jenkins on 
> > > > > https://github.com/jenkinsci/trilead-ssh2.  
> > > > >  
> > > > > I'm then willing to help in implementing this feature in the CLI.
> > > > >  
> > > > > Best regards,
> > > > > Reynald
> > > > >  
> > > >  
> > > --  
> > > You received this message because you are subscribed to the Google Groups 
> > > "Jenkins Developers" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an 
> > > email to [email protected] 
> > > (mailto:jenkinsci-dev%[email protected]).
> > > For more options, visit https://groups.google.com/groups/opt_out.
> > >   
> > >   
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to [email protected] 
> > (mailto:[email protected]).
> > For more options, visit https://groups.google.com/groups/opt_out.
> >   
> >   
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to