I created Jenkins project that have files on SVN (https://repo.xxx.xxx/svn/priv/projectname; certificate is self-signed). My problem is that Jenkins have empty workspace for thi
The solution is pretty easy. I connected to SVN repo from my computer (in command line) as user jenkins. I accepted all certificates permanently (p). This created directory ~/.subversion. I copied this directory to server (wget). And from now everything works just fine.
It looks like Jenkins uses svn credentials cache to authenticate. Those credentials are stored in the ~/.subversion/auth folder. I was struggling because of this and the solution i found was to clean up ~/.subversion/auth folder and then checkout from the console of the machine Jenkins is installed on, append the username Jenkins will use as a parameter. Something like this
svn checkout --username jenkins-svn-user http://svn.server/repo
That will ask for the credentials of the jenkins-svn-user and will store them locally so that Jenkins can use them. Then you can check on your job configuration whether it worked or not.
Hope this helps
Old question, I know. Maybe someone else will find this, though?
I had this problem for awhile, before realizing that I hadn't downloaded the SVN plugin. Even though SVN appears as an option in the Source Code Management section of the configuration screen in Jenkins, the plugin wasn't installed. Hence: https://stackoverflow.com/a/11272158