|
||||||||
|
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/groups/opt_out.
@domi
System setup is uberSvn with httpd.
httpd is setup to require BasicAuthentication over http.
Svn checkout with the same credentials work from several pc's including the server hosting jenkins.
Never the less the subversion plugin in Jenkins can not connect (see previous post).
Jenkins version is now 1.508.
We have succesfully used version 1.504 and 1.505 with some minor bugs on the job configuration pages (saying no access, but jenkins could checkout) and the known subversion cache problems.
Now we upgraded to 1.508 and it is now longer working (already spend 6 hours to fix it and am getting nowhere).
Downgrading didn't help either and now I am concidering never to use this subversion plugin again and switch to a maven scm solution. With 1.504 I also encountered problems with this plugin which took me days to get the credentials set properly by Jenkins.
Please note this my problem is mostlikely caused by a bug in SVN kit self and came along with a Jenkins update that selected the buggy SVN Kit release.