Continuous Integration lava lamps for build notification

The CruiseControl Best Practices Series

by simpsonjulian on April 1, 2008

Continuous Integration can be hard. I work with it every day as a Build & Release Manager. In my role I make sure that we are building our software so it can successfully be
deployed to production. In this series of blog posts I hope to
pass on my top ten tips for using CruiseControl
effectively. I’m writing these with the developers or systems
administrators in mind: the people who most often manage
CruiseControl. However, anybody who is interested in
Continuous Integration will get something from these articles.

Part 1: Publish with a publisher [Chinese translation]
Part 2: Keep your dependencies to yourself [Chinese translation]
Part 3:Configuration the CruiseControl way [Chinese translation]
Part 4: Bootstrap with a bootstrapper [Chinese translation] [Config Validator]
Part 5: Refactor your configuration file [Chinese translation]
Part 6: Scaling up [Chinese translation]
Part 7: CruiseControl for non-Java applications

(Image taken from igb’s photostream on Flickr)

Share with the group:
  • Digg
  • del.icio.us
  • Facebook
  • DZone
  • LinkedIn
  • Slashdot
  • StumbleUpon

Related posts:

  1. Cruise != CruiseControl Newsflash: there are three versions of CruiseControl. The Java One...
  2. Continuous Integration Cage Fight – the entire first series CITCON Europe 2008. Tom Sulston proposes a session for CI...
  3. The quest for a decent Ruby Continuous Integration tool Git has become very popular in the Ruby community. Github...
  4. CruiseControl.rb gets official Git support I’m not a fan, but this is about time: We...

Related posts brought to you by Yet Another Related Posts Plugin.

{ 2 trackbacks }

Refactor your configuration file — The Build Doctor
December 30, 2008 at 11:08 am
2008 in posts — The Build Doctor
December 30, 2008 at 3:33 pm

{ 0 comments… add one now }

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Previous post: CruiseControl Enterprise Best Practices, Part 6: Scaling up

Next post: Ant Best Practices