Jenkins & caching of SVN Credentials

user2208659 picture user2208659 · Mar 25, 2013 · Viewed 10.4k times · Source

Like a lot of people I am banging my head (again) against Jenkins and the subversion plugin. Authenication through the website (enter credentials) fails on authentication. Funny, since I can access svn with the same credentials.

I have deleted:

  • $HOME/.subversion
  • all entries in the hudson.scm.SubversionSCM.xml
  • the svn credentials in the job

What happend that it broke down? I reinstalled the jenkins.war in tomcat and ever since, Jenkins could not access svn anymore.

I've been down this road before and due to the trail-error situation never got to understand how this pain-in-the-arse setup works, to prevent this problem the next time.

Answer

Richard A picture Richard A · Apr 3, 2013

These are the SVN problems I ran into when I moved a jenkins install to another machine.

  1. First, make sure svn commands work for the jenkins user in the console/terminal.

  2. Did you directly copy the config files from the previous install? In my case, the credentials in the config file were hashed and didn't work on a different machine. I deleted the previous config file and started from scratch. After I deleted my old config files, I set the credentials again in the webui.

  3. Are you running Jenkins as a service? Make sure the "Log on as" user for the jenkins service matches the credentials you're using.