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

Re: Subversion is convinced it's commiting, nothing happens, no errors

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-03-28 17:54:05 CEST

Matt Sickler wrote:
> also note that committing doesnt automatically update another working
> copy (assuming that you keep the DocumentRoot as a working copy)
> you need a post-commit hook to do that

Just a personal opinion, but I think it is a mistake to ever
automatically push a commit directly into production. The workflow
should include the option to view/test on a staging location even if you
don't use it every time, and a chance to make several related/dependent
commits before sending to the real server(s). Also, I'd generally
update the production server(s) via a scripted rsync from the staging
location since that makes it easy to skip the .svn directories and push
to any number of production locations.

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 28 17:53:23 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.