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<https://issues.jenkins-ci.org/browse/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 >
