Re: Subversion plugin issues

2012-08-16 Thread Dustin Parker
In hudson.scm.SubversionSCM.xml, I have two entries for my server: ; The whole base64 encoded PKCS12 here; I can't figure out how it's encoded, just get Jenkins to do it The base64 encoded password here and

Re: Subversion plugin issues

2012-08-16 Thread Dallas Clement
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//subversion.credentials I'm still a little unclear on what should go in the certificate

Re: Subversion plugin issues

2012-08-16 Thread Dustin Parker
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 requir

Subversion plugin issues

2012-08-16 Thread Dallas
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