A post-commit hook looks like the trigger event that i'm looking for.
It also looks like it will be very attractive to have a trunk branch which
is what is automatically distributed, while allowing users to create their
own branched versions. Therefore what I'd really like is a way to easily
poll the trunk branch to see if there are any updates and have it be O(1)
with the size of the repository?
On Fri, 17 Nov 2006, Lamont Granquist wrote:
> I'd like to setup a repository which would have the head branch automatically
> synchronized to a set of potentially many geographically distributed servers.
> I do *not* want to synch the entire repo, I just want the head branch.
>
> The implementation plan with CVS would be to use:
>
> - cvsup for a synchronization operation
>
> - triggers to kick off a synchronization operation on a commit
>
> - polling every minute or two with 'cvs history' to determine if the clients
> had missed a trigger event
>
> What would the equivalent actions be in SVN? I've been looking around for
> something like cvsup for SVN that doesn't copy the entire repo and haven't
> been able to find something applicable other than just 'svn update'. I also
> haven't been able to find anything like triggers so far in the svn book.
> Would "svnlook history" run on the root of the repo be good for a lightweight
> polling check to see if anything in the repo had changed since the last 'svn
> update' or is there a better way to do that operation?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 23:14:55 2006