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

Re: Promotion of code

From: Ryan Schmidt <subversion-2006q2_at_ryandesign.com>
Date: 2006-05-06 01:21:26 CEST

On May 6, 2006, at 00:09, Casey Daniell wrote:

> We have 5 graphics guys who develop website content (CSS, XSLT,
> Images)
> for our sites, they currently check in code to Subversion, then each
> one manually moves it to the BETA and PROD environments.
> There has to be a way that we can use Subversion to automatically
> promote code and deploy it to the BETA and PROD envs without having
> all
> users have access to PROD. If this was CVS I would have the graphics
> guys apply a tag to the repository that was named something like for
> BETA or PROD, I could then have a process running that pulls the
> wanted
> tags to the environment, and viola, code is automagically deployed to
> the needed env with a minimum of intervention.
> How can I accomplish this basic idea/task in Subversion? Am I just
> missing the obvious? (I am new to Subversion, used it for 2-3 weeks
> now, but have used CMVC, ClearCase and CVS extensively in the past.)

As I understand it, in CVS, a "tag" is a property of a file. To move
a file to BETA or PROD, you tag the files with that label.

In Subversion tags and branches are implemented as directories. Tags
are meant to be write-once entities (though Subversion does not
enforce this out of the box) and branches are meant to be read-write
entities, so BETA and PROD would best be branches in Subversion
methodology. To move a change from trunk to BETA or PROD, one would
merge the changeset from trunk to the BETA or PROD branch. Merging is
described in the book:


Merging is not an automatic process; it must be done by a human who
can resolve any potential conflicts which may arise.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 6 01:22:23 2006

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.