|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I've been experiencing the error with every checkout attempt, not only externals, and it's persistent. Windows 7 master and slaves. Jenkins 1.565.2 (official latest stable) and Subversion 2.4.3. I decided to upgrade from 1.561/2.0 after encountering some SVN external issues that suddenly occurred (J refused to check out and then complained things were missing).
Although it seems like a pure Subversion issue, downgrading Subversion plugin to 2.0 and 1.5.4 didn't help. Eventually, I upgraded it back to 2.4.3 and manually reconfigured all affected jobs in the above way ... but needless to say, that was a drag^^
Edit:
I found out that Jenkins sometimes tries to connect to the SVN server without actually giving credentials. Here's from the svn server's connection log:
"
190.10.210.20 - jenkins [25/Sep/2014:15:09:06 +0200] ...
190.10.210.20 - jenkins [25/Sep/2014:15:09:06 +0200] ...
190.10.210.20 - - [25/Sep/2014:15:09:06 +0200] ...
190.10.210.20 - - [25/Sep/2014:15:09:06 +0200] ...
First two checkouts succeeded, last two didn't.