[ 
https://issues.apache.org/jira/browse/WHIMSY-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved WHIMSY-304.
-------------------------
    Resolution: Fixed

The following commit(s) were added to refs/heads/master by this push:
     new a745709  WHIMSY-304 - only checkout needed files
a745709 is described below

commit a74570990a8805079a29e2b2f6a3775d4c4982df

    WHIMSY-304 - only checkout needed files
---
 Rakefile                   | 25 ++++++++++++++++-
 repository.yml             | 11 ++++++--
 www/status/monitors/svn.rb | 68 ++++++++++++++++++++++++++++++++++++++++++++--
 3 files changed, 99 insertions(+), 5 deletions(-)


> Don't check out entire  SVN directory where only a few files are needed
> -----------------------------------------------------------------------
>
>                 Key: WHIMSY-304
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-304
>             Project: Whimsy
>          Issue Type: Improvement
>            Reporter: Sebb
>            Priority: Major
>
> There are some individual files that Whimsy uses, e.g. apmail/bin/.archives
> However the entire directory is checked out.
> This seems unnecessary.
> svn update can equally be used to update just a few files.
> If the directory is checked out as empty, the required files can be added 
> using 
> 'svn update files...'
> Subsequent 'svn update' ccommands will update the files that are present.
> The 'rake svn:update' task can be updated to support a list of files defined 
> in repository.yml
> Note that at present, the depth is only used when the initial checkout is 
> made.
> Subsequent changes do not affect the checkout (except for depth==delete).
> This has the advantage that testers can checkout an empty directory and be 
> assured that it won't be replaced by the next run of the update task.
> The proposed process is:
> If the checkout depth in the yml file is empty, but the current checkout is 
> not empty, then:
> svn update --set-depth empty
> The list of files can then be checked out using
> svn update files...
> This should minimise the downtime, and allow a live system to be migrated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to