[
https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162555#comment-162555
]
Kohsuke Kawaguchi commented on JENKINS-11933:
---------------------------------------------
Thanks centic for digging deeper into this. It sounds like a work around is to
avoid using that particular overloaded form of the doList method so that we can
pass in {{SVNDepth.IMMEDIATES}}?
> Subversion plugin doesn't probably work correctly with svn server version
> 1.7.1
> -------------------------------------------------------------------------------
>
> Key: JENKINS-11933
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Affects Versions: current
> Environment: svn server 1.7.1
> ubuntu
> Reporter: Nikita Aznauryan
> Priority: Blocker
> Labels: plugin
> Attachments: 0001-imported-1.3.7.patch,
> 0002-Adjust-version-number-in-pom.patch,
> 0003-update-version-and-add-second-maven-repository-to-ge.patch,
> 0005_subversion_plugin_svnkit_1_3_7.patch, subversion-svnkit-1.7.4.hpi,
> subversion.hpi
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for
> hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
