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

RE: RE: web development revisited

From: Rob van Oostrum <rob.vanoostrum_at_blastradius.com>
Date: 2006-03-27 23:33:45 CEST

What Sean said re. CruiseControl.

Also, using a branching model rather than a tagging model to push code
out to Staging and Production (Live) seems like overkill. If a problem
arises in Staging you'll typically want to go back, fix the problem and
verify in Development again before pushing out another build to Staging.
So there is typically nothing you'd want to change directly on a Staging
branch, but rather you'd make the change in Development and promote
another Staging build by re-tagging at the revision of the fix.

Of course, tags and branches being that by convention/semantics in SVN,
nothing needs to be stopping you from treating the tag as a branch
should you ever be faced with a time-sensitive emergency.

Cheers
Rob

> -----Original Message-----
> From: Foy, Sean [mailto:Sean.Foy@TycoHealthcare.com]
> Sent: Monday, March 27, 2006 4:22 PM
> To: 'Jamie'; users@subversion.tigris.org
> Subject: RE: web development revisited
>
> > going to be setting up a system for web development. I have been
> ...
> > - Automated website updating (as far as possible)
> ...
> > The staging and live branches will not update the websites
> > automatically, this will be performed through a web based interface.
> ...
> > - is it possible to have a post-commit hook run a different command
> > depending on the branch thats being committed?
>
> Have you heard of continuous integration? I suggest that you consider
> augmenting SVN with another program such as CruiseControl
> (http://cruisecontrol.sourceforge.net/). Your diagram looks fine as
far as
> SVN goes, but it sounds like you are trying to use post-commit hooks
to
> automate deployment. Automated build systems can solve related
problems
> such
> as:
> - monitoring the SVN repository for changes
> - compiling your program in a standardized environment
> - regression-testing your software
> - communicating to relevant parties about the status of your code
> - deploying software (conditionally on tests and other criteria) to
the
> right machines
>
> ---------------------------------------------------------------------
> 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 Mon Mar 27 23:35:12 2006

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