On 04 Feb 2013, at 5:38 PM, Graham Leggett wrote:
> 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:
On 04 Feb 2013, at 5:38 PM, Graham Leggett 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 th
On 04 Feb 2013, at 4:50 PM, Andreas Schilling
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
> knowi
D-Nr.: DE147841145
Von:Graham Leggett
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 Jenkin
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 Jenk
