Jenkins Subversion Error - E200015: No credential to try. Authentication failed

Question

I\'ve updated the Subversion plugin of jenkins to version 2.2

Now i get following error for repos which build the first time after the upgrade and for repos where someth

Answer 1

Ok after many comments on the official bug report we were able to solve this issue.

So to get it working you have to update to the newest 2.3-snaptshot of the subversion plugin, which can be found here:

https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/

(Download the .hpi file and install it on your jenkins)

1. After that you have to fix your build. I've written a small tutorial on how you can do this here.
2. open the build configuration
3. scroll down to the source-code-management section
4. click on the "Add additional credentials..." button
5. define as realm the specific identifier for our svn server --> ( Company Subversion Repository)
6. • if it should work for a different svn you need to use the realm of this server
7. • checkout a repo on this server via the command-line --> svn --username {username} --password {password} checkout prot://ip:port/svn/repo <-- you can cancel this after it has started the checkout
8. • read all realms available on your mac with this cmd --> find ~/.subversion/auth/svn.simple/ -type f -exec cat {} + | grep -A 2 realmstring
9. • • there's also another option to get the realmstring. on a pc which was not connected to the svn before, do the following in the therminal: "svn info prot://ip:port/pathtorepo" --> this will output something like "Authentication realm: Company Subversion Repository"
10. select the credentials --> buildmaster/****** ( Company Subversion Repository)

NOTE : If you are using svn+ssh, your realm would look like "svn+ssh://server-name" without double-quotes. No pointy brackets, port or realm name needed.

11. save and be happy!