You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Adam Walling <ad...@gmail.com> on 2011/12/16 19:53:21 UTC
Updating a new branch with existing files from filesystem in 1.7
When creating a new branch, obviously everyone will need to download it for
maintenance and etc. The naive approach is to simply update and download
the new branch from the server. However, with a large branch and with many
users simultaneously updating, this quickly overloads the bandwidth and may
end up takings hours to complete.
With 1.6, we would take advantage of being able to copy all of trunk to the
new branch directory on the local filesystem, and then switch to the actual
branch URL and update, therefore only transferring files that actually
differ. This is pretty much the process touched upon in the svnbook
http://svnbook.red-bean.com/en/1.7/svn.branchmerge.switchwc.html
In 1.7 this does not seem to be possible, since there are no entries in the
database for the local copies.
I've tried a few different approaches but all seem to end up downloading
everything from the server. We use TortoiseSVN primarily, as well as the
usual command line tools. I know using sparse checkouts can help with not
having to download what is not needed, but the paths we need are still
quite large. I know I can switch the existing working copy to the new URL
as well, but I need to be able to work on both.
Despite a few hours of searching through Google and the mailing lists, I've
come up with nothing, not even a solid answer on whether this is still
possible or not. It seems that there must be some way to
I have a feeling I am overlooking something simple. Regardless, how should
one handle this situation? Am I stuck downloading a few gigabytes over a
relatively slow connection?
Thanks for any help,
--
- Adam D. Walling
Re: Updating a new branch with existing files from filesystem in 1.7
Posted by Stefan Sperling <st...@elego.de>.
On Fri, Dec 16, 2011 at 01:53:21PM -0500, Adam Walling wrote:
> When creating a new branch, obviously everyone will need to download it for
> maintenance and etc. The naive approach is to simply update and download
> the new branch from the server. However, with a large branch and with many
> users simultaneously updating, this quickly overloads the bandwidth and may
> end up takings hours to complete.
>
> With 1.6, we would take advantage of being able to copy all of trunk to the
> new branch directory on the local filesystem, and then switch to the actual
> branch URL and update, therefore only transferring files that actually
> differ. This is pretty much the process touched upon in the svnbook
> http://svnbook.red-bean.com/en/1.7/svn.branchmerge.switchwc.html
>
> In 1.7 this does not seem to be possible, since there are no entries in the
> database for the local copies.
I am not sure why you are seeing a problem here.
1.7 working copies can be copied and then switched. Just be careful not
to copy the sqlite database (.svn/wc.db) while it is being accessed.
See http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng
What are you basing your assumption on?
Did you try out your procedure with 1.7 and run into some problem?
Re: Updating a new branch with existing files from filesystem in
1.7
Posted by Ulrich Eckhardt <ul...@dominolaser.com>.
Am 16.12.2011 19:53, schrieb Adam Walling:
> When creating a new branch, obviously everyone will need to download
> it for maintenance and etc.
No, only those that are actually using that branch and working on it
somehow need it.
> The naive approach is to simply update and download the new branch
> from the server. However, with a large branch and with many users
> simultaneously updating, this quickly overloads the bandwidth and
> may end up takings hours to complete.
What kind of setup do you have? If the users are on a LAN, you could
speed up using caching with svnsync.
> With 1.6, we would take advantage of being able to copy all of trunk
> to the new branch directory on the local filesystem, and then switch
> to the actual branch URL and update, therefore only transferring
> files that actually differ. This is pretty much the process touched
> upon in the svnbook
> http://svnbook.red-bean.com/en/1.7/svn.branchmerge.switchwc.html
>
> In 1.7 this does not seem to be possible, since there are no entries
> in the database for the local copies.
Yes, this still works. The fault is that you are checking out the whole
repository root instead of just those parts you are working on.
Therefore everybody has parts they don't need and everybody pays the
price (HD storage, update complexity) for things they don't really want.
Uli
**************************************************************************************
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
Re: Updating a new branch with existing files from filesystem in 1.7
Posted by Les Mikesell <le...@gmail.com>.
On Fri, Dec 16, 2011 at 12:53 PM, Adam Walling <ad...@gmail.com> wrote:
>
> With 1.6, we would take advantage of being able to copy all of trunk to the
> new branch directory on the local filesystem, and then switch to the actual
> branch URL and update, therefore only transferring files that actually
> differ. This is pretty much the process touched upon in the
> svnbook http://svnbook.red-bean.com/en/1.7/svn.branchmerge.switchwc.html
>
> In 1.7 this does not seem to be possible, since there are no entries in the
> database for the local copies.
You should still be able to copy a whole working copy. When you say
'copy all of trunk', is that the whole working copy or are there more
directories above trunk' in your checkout?
--
Les Mikesell
lesmikesell@gmail.com