Summary

CruiseControl is a relatively simple but powerful tool. It doesn't try to do too much, but what it does, it does wellautomating the execution of your builds and reporting on their results. Since CruiseControl has been around for a few years, it has reached a level of acceptance and maturity such that I would have no problem recommending it for use on most projects. I have tried to cover the most common configuration scenarios and best practices for CruiseControl in this chapter:

• Configuring the CruiseControl Build Results web

• Integrating ClearCase and CruiseControl for labeling or baselining

• Defining different build schedules

• Publishing build results via e-mail, FTP, or Ant

However, this list is subjective, and I did not cover every aspect of CruiseControl in either this or the preceding chapter. I therefore encourage you to examine the information that is available on the CruiseControl Wiki at http://confluence.public.thoughtworks.org/display/CC/Home. Or you can subscribe to the CruiseControl users mailing list, available at http://sourceforge.net/mailarchive/forum.php?forum_id=2203.

Now that I have completed the discussions of CruiseControl and the Build Execution phase, we can move on to the next phase of the integrated build and release life cyclereporting. In particular, we will look at how to generate reports on ClearCase baselines and ClearQuest change requests.