DamageControl vs. CruiseControl
Erik Thauvin links to a blog entry by Guillaume Laforge which covers the continuous integration tool DamageControl. The concept of Continuous Integration means that a dedicated server will create nightly (or daily or hourly) builds of your software project and you can keep track of the build status because website lists all your projects that build or won't build and you will receive an email, if one of your teammates has checked in some code that will break the build process.
Continuous Integration has been described by Martin Fowler who is one of the authors of CruiseControl, a CC-tool I have been using before.
The interesting question is "What is the important difference between CruiseControl and DamageControl"? The documentation for both projects is quite terse, but there are helpful Wiki pages for CruiseControl and DamageControl. As far as I can see offers DamageControl to be started from a remote server, e.g. by a CVS trigger (I will have to find out if this works with subversion, too). Additionally they offer nice status graphics that can be included into your homepage. DamageControl's configuration files are written in YAML and they look much simpler than CruiseControl's.
I am Product Manager for Collaboration and Digital Asset Management at