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

Re: Pushing asynchronous changes to production

From: Jim Thompson <jim.thompson_at_doit.wisc.edu>
Date: 2007-01-26 16:50:53 CET


Just curious - do you have a way to enforce this?

> nothing _should_ be in trunk that's not ready to go on prd.

We're coming from CVS, where we use the taginfo filter. We let regular
developers commit anything they wish and they can tag files "test"
and/or "testdemo". Only certain folks (not developers) are allowed to
manipulate qa, prod or demo tags. We also have more tags that are
maintained by scripts. Then we have tags for our framework (vs. app)
files - currently 7 different environments. Config files sometimes have
up to 8 branches.


Russ wrote:

>We develop Websites too and use svn. Production is just a checkout of trunk, and nothing should be in trunk that's not ready to go on prd.
>You can btw update individual files at least with TortoiseSVN.
>Sent wirelessly via BlackBerry from T-Mobile.
>-----Original Message-----
>From: Janine Sisk <janine@furfly.net>
>Date: Thu, 25 Jan 2007 16:12:49
>To:Subversion List <users@subversion.tigris.org>
>Subject: Pushing asynchronous changes to production
>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.
>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 Jan 26 16:51: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.