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

Re: web development revisited

From: Jamie <jam5t3r_at_gmail.com>
Date: 2006-03-28 00:17:23 CEST

I had not heard of continuous integration before, thanx for the link.
So cruseControl will look for changes in my svn repository and update
the website automatically, and I would use this in place of the post-
commit hooks for the development and special project branches? Or are
you suggesting I use cruseControl to deploy to the staging and live
sites also?

On 27 Mar 2006, at 13:21, Rob wrote:

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

Rob, that sounds logical, I havent looked into tagging very
extensively yet, I will do this now.


On 27 Mar 2006, at 13:21, Foy, Sean wrote:

>> 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
Received on Tue Mar 28 00:18:18 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.