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

Pushing asynchronous changes to production

From: Janine Sisk <janine_at_furfly.net>
Date: 2007-01-26 01:12:49 CET

I found a few people asking this question, and could probably have
found more if I'd known the right keywords to use, but didn't find
any really satisfying answers.

We have a fairly typical development/production website setup. Under
CVS we tagged the files that were ready to go to production with
"stable", and then (because the production site was created via a
checkout on the stable tag initially) used cvs update to move them to
production. This is easily scripted for the less technical user, and
has worked well for us. Each person can move only their changes
without knowing or caring if someone else has checkpointed their work
by committing but is not ready to go live with it yet.

The question is how to emulate this setup in svn. It's not possible
to tag only the commits you want moved to production anymore, and
making a branch for every little change is not very practical.

One person suggested passing a filename and revision number to a
script that would update the file to that revision, but as far as I
can tell "svn update" doesn't take filenames, only directories, so
I"m not sure how to do that.

I know there are many home-grown solutions to this problem out there,
and I'd love to hear about them, but it seems there should be a
recommended way to handle it and I haven't been able to find it, if
it exists.

thanks,

janine

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 26 01:13:17 2007

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