Promotion of code

[Casey Daniell <ca...@hotmail.com>]

Ok I am at a loss on how to do this, but I know this isn't a unique or
hard problem any assistance, or direction is appreciated.

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.)

Many Thanks for any help,

Casey 
_________________________________________________________________
Join the next generation of Hotmail and you could win the adventure of a lifetime
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Promotion of code

[Ryan Schmidt <su...@ryandesign.com>]

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:

http://svnbook.red-bean.com/en/1.1/ch04.html

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