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

Re: advice for commit/updates

From: John Peacock <jpeacock_at_rowman.com>
Date: 2007-07-16 20:46:49 CEST

Brian Krusic wrote:
> What's the best way to automate updates once a commit has occurred?

That would be a post-commit script. ;-)

Depending on your needs (single update, multiple updates, local vs
remote sites), you may want something more capable than a home-brewed
script. You might want to consider a module I wrote, SVN::Notify::Mirror:


which makes it very easy to keep multiple working copies in sync with
changes to the repository. It includes the ability to keep multiple web
sites up to date on multiple servers, for example.

For example, we have a little more than a dozen active web sites, each
with their own trunk development (mirrored to the test server) and each
with their own production server. All updates are performed in the most
efficient way (i.e. a commit deep in a tree will only update those
files). The production server is automatically updated to the latest
tag for that site; no manual interaction with the web server is required.



John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 16 20:46:19 2007

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.