|
||||||||
|
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 upgraded Visual SVN Server to 2.7.7 and now I get this error on every job in Jenkins. I am able to check projects out with TortoiseSVN, I am able to log in to the Visual SVN website directly through a browser.
I have a Windows Server with the Jenkins site on. If I try to configure the job to check files out I get this error message when supplying credentials. I've tried via the Job Configuration page and the Credentials page. The slave nodes are unable to checkout either.
I have seen suggestions to add -Dsvnkit.http.sslProtocols="SSLv3 to the service, it said to add it to the jar command but the service on the slave nodes is an executable. I followed some instructions and added it to the slave config XML, that didn't work. (http://www.tikalk.com/alm/jenkins-svn-integration-bugs-and-workarounds) When I do svn checkout <path to project> I can check the files out but I don't get asked about a certificate. (I'm using the SVN from Tortoise for that.)
Some suggest running svn from the command line but the machines don't have it without installing something like TortoiseSVN. I tried installing Tortoise and running it from there, I got the Subversion\auth folder they were talking about but it still doesn't work.
Another said to modify the subversion config but didn't say where that is.
Any helpful suggestions gratefully received, if you need more info let me know.