Re: Antwort: Jenkins + Subversion + SSL client certificates
On 04 Feb 2013, at 5:38 PM, Graham Leggett minf...@sharp.fm wrote: Is there a way to get rid of svnkit entirely? In our case the native svn client works fine, we don't need this second client, it doesn't seem to work properly with digital certificates and/or SNI and has no error handling at all. To the credit of the svnkit project, they have added SNI support to the latest trunk of svnkit, and have confirmed it works when used with Java 7 (which supports SNI). Regards, Graham -- smime.p7s Description: S/MIME cryptographic signature
Jenkins + Subversion + SSL client certificates
Hi all, Does there exist a definitive description on how to set Jenkins up to talk to a subversion repository that is protected by SSL client certificates? The native subversion client works perfectly, but the svnkit based client refuses to connect, failing with a handshake error. Does the Jenkins Subversion plugin look at the native subversion configuration at ~/.subversion/servers? Does the plugin look somewhere else? I have trawled the Jenkins UI, and apart from a few boilerplate options in the configure section there is no way to configure svn authentication at all. Is it supposed to be like this or am I doing something wrong? Regards, Graham -- -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Antwort: Jenkins + Subversion + SSL client certificates
Hi Graham, you know of http://YOURJENKINSINSTANCE/scm/SubversionSCM/enterCredential ? To my current knowledge this URL is still kind of unknown. At least when we set up SVN (like 2 years ago) we stumbled upon this more by accident than by knowing... After switching to hg some time ago I actually don't know alot about what's happening around the SVN integration in Jenkins, but I think this still is the way to pass the credentials. Kind regards, Andreas Schilling CAE Processes Data Management --- Dipl. Inf. Andreas Schilling Senior Software Architect TWT GmbH Science Innovation Bernhäuser Str. 40 - 42 73765 Neuhausen Tel: +49.7158.17 15.6 73 Mobil: +49.1 72.6 22 88 70 E-Mail: andreas.schill...@twt-gmbh.de www.twt-gmbh.de Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (Stv.), Frank Beutenmüller (Stv.) Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778 Umsatzsteuer: ID-Nr.: DE147841145 Von:Graham Leggett minf...@sharp.fm An: jenkinsci-users@googlegroups.com Datum: 04.02.2013 15:43 Betreff:Jenkins + Subversion + SSL client certificates Gesendet von: jenkinsci-users@googlegroups.com Hi all, Does there exist a definitive description on how to set Jenkins up to talk to a subversion repository that is protected by SSL client certificates? The native subversion client works perfectly, but the svnkit based client refuses to connect, failing with a handshake error. Does the Jenkins Subversion plugin look at the native subversion configuration at ~/.subversion/servers? Does the plugin look somewhere else? I have trawled the Jenkins UI, and apart from a few boilerplate options in the configure section there is no way to configure svn authentication at all. Is it supposed to be like this or am I doing something wrong? Regards, Graham -- -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Antwort: Jenkins + Subversion + SSL client certificates
On 04 Feb 2013, at 4:50 PM, Andreas Schilling andreas.schill...@twt-gmbh.de wrote: you know of http://YOURJENKINSINSTANCE/scm/SubversionSCM/enterCredential ? To my current knowledge this URL is still kind of unknown. At least when we set up SVN (like 2 years ago) we stumbled upon this more by accident than by knowing... After switching to hg some time ago I actually don't know alot about what's happening around the SVN integration in Jenkins, but I think this still is the way to pass the credentials. I finally stumbled on a way to put the certificate in on a per project basis (highly non ideal, but I'll take anything that works at this point). Still no joy. The error I get is this: Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake The remote host disconnects because of this: SSL Library Error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number All of these are deep protocol errors that are just dumped in a logfile, the actual error is discarded or ignored. Is there a way to get rid of svnkit entirely? In our case the native svn client works fine, we don't need this second client, it doesn't seem to work properly with digital certificates and/or SNI and has no error handling at all. Regards, Graham -- smime.p7s Description: S/MIME cryptographic signature
