Continuous integration tools - JUnit in Action - page 177

Figure 11.3 CruiseControl control panel in the browser

CruiseControl also provides a way to control your scheduled builds through a nice
GUI , by starting a Jetty instance. By default, this Jetty instance is started on port 8080,
but you can change it (in case that port is already taken). To do so you need to
change the port property in your jetty.xml file in the etc folder. For our purposes we
start CC on port 8888. You can check the GUI by visiting http://localhost:8888/
cruisecontrol/ in a browser. You should be able to see something like the screen dis-
played in figure 11.3. As you can see, there some nice details on how many builds
were iterated, some detailed statistics on how many of them failed, and, of course, the
JU nit logs. There's also an RSS feed that you could subscribe to, to get the results
from the execution.
Let's move on. Some things are working, but currently the way they are doesn't
give us much data. If we look in the console or the GUI , we can see that the build is
going well, but it's a tedious task to look there all the time. What if we had some way to
get the results from the execution directly into our email or, even better, get the email
from CruiseControl only in case things go bad?
This is possible, and all we have to do is add another publisher in our config.xml.
The section we want to add is shown in listing 11.2.

Listing 11.2 CruiseControl's htmlemail notification

<htmlemail
mailhost="your.company.smtp.host"
returnaddress=” [e-mail]”
buildresultsurl=" http://localhost:8888/buildresults/connectfour/"
css="/home/peter/my-very-own-css/cruisecontrol.css"
logdir="logs/connectfour">
<map alias="developers" address="connectfour- [e-mail]" />
<map alias="manager" address=" [e-mail]" />

C

B

D

E