[
https://issues.jenkins-ci.org/browse/JENKINS-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163658#comment-163658
]
Steven Lee commented on JENKINS-2556:
-------------------------------------
Just ran into this too and it takes way too long to delete everything and then
check it out again.
We have a large amount of static files (mp3, mov, etc.) in subversion which are
deployed to apache.
> Use svn switch where applicable
> -------------------------------
>
> Key: JENKINS-2556
> URL: https://issues.jenkins-ci.org/browse/JENKINS-2556
> Project: Jenkins
> Issue Type: Patch
> Components: subversion
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: rombert
> Attachments: subversion.diff, subversion2.diff, subversion3.diff
>
>
> When updating the 'stable' builds of our projects, I update the repository URL
> from svn://aaa/project/branches/182 to svn://aaa/project/branches/183 ( for
> instance ).
> This results in a clean checkout ( Checking out a fresh workspace because the
> workspace is not svn://aaa/project/branches/183 ), which takes somewhere
> around
> 30 (!) minutes, when a svn switch would've taken a few seconds.
> What I suggest is a (perhaps per job configurable) setting which would use svn
> switch if all but the last {x} path elements are the same.
> For instance, a setting of 1 would allow switch to be used for
> svn://aaa/project/branches/183 -> svn://aaa/project/branches/184
> but not for
> svn://aaa/project/branches/183 -> svn://aaa/project/trunk
> A setting of 2 would allow switch to be used for both.
> A setting of 0 would disallow the usage of svn switch.
--
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
