CODEWITHSUNDEEP
svnauthenticationjenkinsjenkins-plugins
doc
doc

Reputation: 289

Jenkins Subversion plugin credentials error

I have configured a Jenkins project to work with my Subversion repository, but after entering the proper credentials through the Jenkins interface (and successfully authenticate) the subversion plugin apparently is not finding the credentials.

This is the error I'm getting:

Unable to access https://... : svn: E200015: OPTIONS ... failed org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS ... failed ... Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed ...

I looked on the Jenkins folder and the file hudson.scm.SubversionSCM.xml contains the credentials as expected.

The weird thing is I entered the credentials manually using TortoiseSVN, and those were saved on my AppData...\Subversion\auth\svn.simple, and after doing that Jenkins can connect to the repo. But I don't want to do that for every repository. It seems to me that the Jenkins plugin is looking for the credentials at the svn folder instead of the Jenkins directory first.

I appreciate your comments and help. Thanks.

Upvotes: 5

Views: 2422

Answers (1)

lax1089
lax1089

Reputation: 3473

As mentioned in comment above, the method that the Jenkins Subversion plugin uses to identify its associated credentials has been changed with version 2.0 and above.

Upgrade the plugin to the current version. Jenkins should then successfully connect to your various repositories without you having to manually enter them (via TortiseSVN).

Upvotes: 0

Related Questions