[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Two-Site Subversion Repository Setup Ideas

From: Andreas Krey <a.krey_at_gmx.de>
Date: Mon, 6 Jun 2011 13:22:57 +0200

On Sun, 05 Jun 2011 14:57:22 +0000, Randolph, Christian [USA] wrote:
> Is there a way to setup the two subversion repositories to somehow automate keeping the two repositories in sync?

No (AFAIF, as usual), not out of the box.

> We are usually passing media back and forth once a week, but currently we are doing a manual sync process that is both time-consuming and error-prone.

I don't think that there is a way of synchronizing all branches of two
svn repositories when different commit are made to each of them.

It would be relatively easy to keep a single branch (say, trunk)
synchronized with its brother on the other side, by carrying the
tree back and forth, and doing some script magic. You need to
remember the last revision you transported, though. (You will
also lose renames, and svn:externals will be interesting.)

The 'vendor model' won't work because it does not work with cyclic
imports; it does not give the merge infos that are needed in this case.

> Any suggestions would be greatly appreciated.

The 'dirtiest' model of synchronization is to use git&svn in the same
sandbox, with proper .ignores, and use the git repos for transfer.
But that by itself is also somewhat error-prone. I use that on svn
projects when I need to work on multiple machines, but it's not an
industrial method.


"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Received on 2011-06-06 13:23:33 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.