Hello Dustin, Thanks a ton! This is the exact dilemma I have run into. Do you mind posting the contents of these two files on your system?
/var/lib/jenkins/hudson.scm.SubversionSCM.xml /var/lib/jenkins/jobs/<jobname>/subversion.credentials I'm still a little unclear on what should go in the certificate and userName fields. Should the certificate field specify a path to the cert file? It sounds like the userName field needs to contain the realm info also. On Thu, Aug 16, 2012 at 1:07 PM, Dustin Parker <[email protected]> wrote: > See this issue: > > https://issues.jenkins-ci.org/browse/JENKINS-3912 > > and this forum post: > > https://groups.google.com/d/msg/jenkinsci-users/uA4dtvlMsCQ/FAwo2y4pI8MJ > > > On Thursday, August 16, 2012 7:36:18 AM UTC-7, Dallas wrote: >> >> I'm trying to setup Jenkins to attach to a subversion repo that requires >> username/password as well as a https/pkcs#12 client cert file and >> passphrase. Unfortunately, the subversion scm config presents a radio >> button with the following choices: username/password, SSH public key, or >> HTTPS client cert. I've opened an issue about this JENKINS-14792. But I am >> seeking some more immediate relief and wanting to find a workaround or a way >> to hack the subversion plugin. Can anyone point me in the right direction? >> >> Thanks
