We are experiencing the same behavior.
When the credentials are entered from the config page and successfully
validated, they are stored in
$JENKINS_HOME/jobs/$JOB_NAME/subversion.credentials (or
$JENKINS_HOME/hudson.scm.SubversionSCM.xml if you use global credentials)
<?xml version='1.0' encoding='UTF-8'?>
<hudson.scm.PerJobCredentialStore>
<credentials class="hashtable">
<entry>
<string>< https://subversion.xxxxx.com:443> wandisco
<https://subversion.xxxxx.com:443>> </string>
<hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
<userName>xxxx</userName>
<password>yyyy</password>
</hudson.scm.SubversionSCM_-DescriptorImpl_-PasswordCredential>
</entry>
</credentials>
In our case the issue arises because the stored authentication realm
("wandisco") does not match the realm in the httpd svn DAV and supplied on
the 401 response header ("Subversion Repository"). This is why Jenkins
cannot find a valid credentials entry (Host + Realm) to try.
<Location /svn>
DAV svn
SVNParentPath /var/svn/repositories
SVNListParentPath On
SVNReposName "Subversion Repository"
AuthType Basic
AuthName "Subversion Repository"
HTTP/1.1 401 Authorization Required
Date: Fri, 30 Aug 2013 14:25:46 GMT
Server: Apache/2.2.15 (Red Hat)
WWW-Authenticate: Basic realm="Subversion Repository"
Content-Length: 479
Content-Type: text/html; charset=iso-8859-1
Keep-Alive: timeout=500
Connection: Keep-Alive
Now the question is how to resolve (or is this an issue in the Jenkins
Subversion Plug-in).
Jenkins - 1.480.3
Jenkins Subversion Plug-in - 1.50
-----
Arthur Herman
The Home Depot - Information Technology
Lead Developer - Application Platforms/Development Tools
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/SVN-Checkout-failing-on-Jenkins-slave-servers-tp4656522p4677232.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
