Managed to do this again in Jenkins 1.490 with svn plugin 1.43. This time the error in the UI was "handshake error".

The jenkins subversion plugin now runs a version of svnkit 1.7.4, again patched. Clearly client cert AND credentials is not part of the testing.

The workaround again because I think my earlier posts are a bit unclear:

  • Remove (backup) jenkins' existing .subversion dir. For me it is /var/lib/jenkins/.subversion
  • Try authentication in the UI, jenkins will cache your server cert in a fresh .subversion
  • Upload client cert in the UI, with password – error
  • In jenkins .subversion/servers file configure ssl-client-cert-file and ssl-client-cert-password as for any other svn client
  • As a user with write access to jenkins .subversion (I used root), run a standalone svnkit. I used version 1.7.6.
  • Commmand: ./jsvn info https://my.server/svn/proj/ --config-dir=/var/lib/jenkins/.subversion --username=your-svn-user

This command immediately produced a prompt that let me confirm that I want to store the client cert pass phrase in plaintext. I didn't even have to type the pass phrase, so it must have gotten it either from the upload or from the config file. After that I was prompted for svn password and confirmation to store in plaintext. After that my jenkins build run.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to