RE: Re: Promotion of code

Your exactly correct about how tags operate in CVS, I was thinking of having each graphic guy on their own branch and performing some kind of scripted merge from their individual branches to the BETA branch, which would automatically be deployed to that env. Then once the code has been tested moved to PROD branch for deployment, however, I don't have the bandwidth to do the merges for them, and they won't do the merges themselves.
 
I was thinking there has to be some other way to accomplish this task, but this is the only thing I am come up with so far....
 
Casey

> CC: users_at_subversion.tigris.org> From: subversion-2006q2_at_ryandesign.com> Subject: Re: Promotion of code> Date: Sat, 6 May 2006 01:21:26 +0200> To: casey_daniell_at_hotmail.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.> > > >
_________________________________________________________________
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
Received on Sat May 6 19:55:29 2006