Continuous integration tools - JUnit in Action - page 176

previously, we publish the result from the build (the .jar file from the target folder)
into the artifacts folder. We do that only if the result from the execution is successful
(see the onsuccess element).
So far, so good—we're able to start CruiseControl, and according to the config-
uration in the listing, it will build our project every 300 seconds (if there's a change
in the source control system). So let's do it. Navigate to the $ CC_HOME folder and
start the CruiseControl server by issuing the following command:

cruisecontrol.bat
Or in case of UNIX , 3 execute

./cruisecontrol.sh
CruiseControl will be executed and will look for the config.xml file to read. If you've
done everything right, after execution you should see something similar to figure 11.2.
Now it's time to make a change in the repository, and hopefully after 300 seconds
you'll see the build being executed again.
Here's an interesting question: how often should you build your projects? This is a
tough question, and it all depends on you and on the time you need to make a new
build. It makes little sense to make a build every minute when you need more than a
minute to execute the build itself. Keep in mind that this is a book about software test-
ing, and we all propagate a lot of testing, using not only JU nit but also all kinds of inte-
gration and functional testing tools. This means that production builds tend to be
time consuming.

Figure 11.2 Executing CruiseControl for the first time

3

You need to check to make sure that the .sh script has executable modifiers set.