Re: web development revisited

Another tool that does this stuff is BuildBot. It allows various "change
sources" to be set up (either 'push' or 'pull' modes are OK), then
various sequences of updating, building and testing to be performed. It
can manage various "build slaves". In your case you might be able to use
it with your live and staging websites as build slaves. Might be worth
checking it out as well. I found it very flexible, and it's all
python-based so if you prefer python you might find it easier.

http://buildbot.sourceforge.net/

Cheers
JP
> 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.
>
> Cheers,
> Jamie
>
>
> 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
>
>
>
> --No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.2/293 - Release Date: 26/03/2006
>
>

-- 
John Pye
Department of Mechanical and Manufacturing Engineering
University of New South Wales, Sydney, Australia
http://pye.dyndns.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org