|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
This was neither a user error or nor a fluke. Rather a problem easy to reproduce. Run a basic Subversion 'svnserve' server, create a basic project in Jenkins/Hudson and use URL like 'svn://localhost/path/to/my/svn/repo'. When doing so, Jenkin/Hudson reports that repository '/path/to/my/svn/repo' does not exist.
The first Jenkins release which allows to use protocol svn:// is 1.514 released May 1st, 2013. The problem is as such not mentioned in the ChangeLog, it appears that upgrading to a less buggy svnkit version must have overcome a problem which should never have existed in the first place.