|
YOUR FEEDBACK
Did you read today's front page stories & breaking news?
SYS-CON.TV |
TOP THREE LINKS YOU MUST CLICK ON Tips and Tricks CruiseControl: The Complete Continuous Integration
CruiseControl: The Complete Continuous Integration
By: Ronen Lewit
Dec. 17, 2002 12:00 AM
A continuous integration process involves automatic building and testing with tools like Ant and JUnit. These tools need a tool that will manage and control the build process - this is where Cruise Control comes in. CruiseControl, an open source tool from SourceForge, is a framework for a continuous build process. It provides an easy-to-use tool that integrates Ant, JUnit, and others to provide a simple utility that builds and tests your software throughout the development cycle. For a complete build process you might want to clean the build directory, fetch sources from the source configuration tool, compile sources, package applications, start the application server, deploy the packaged applications, perform tests, generate reports, and clean up. Simpler (intermediate) build processes can pass the clean task and part of the test tasks. All of these tasks should be part of your Ant build configuration. For an easy transition between different dev/test/prod environments it's helpful if you use different configuration settings for your application properties and application server settings and let Ant prepare these settings for you. For example, for the build.xml:
<filter token="server.domain" And for the config.xml:
<Domain Name="@server.domain@"> where all server.* properties reside in different configuration files for use with any different environment (dev.properties, test.properties, etc.) This will put you in a position where you could run continuous build process without human hands. Now, let's see how CruiseControl helps us with these builds.
CruiseControl, release 2.0, is more flexible and open. Its building blocks are plug-ins (that you can always extend or replace). It is shipped with several plug-ins that, in most cases, will do the work without the need for an update. The provided plug-ins are grouped into five types:
CruiseControl generates a log file for each build process. This log file can be used to follow the build results as well as publish them using the publishers. CruiseControl comes with a prepared Web application that enables you to publish your build results on an intranet site. In order to install the Web application, you should follow the installation instructions and pay special attention to the replacement of the log path element in the web.xml file and the correct jsp version usage in the buildresults.jsp file.
After you have configured the Web application, you can install it on your target intranet Web server. Make sure this server shares a file system with the process, so the CruiseControl process can update this Web application. The generated report can include information about:
The CruiseControl Web application simply takes the log file generated by the build process and transforms its format for a clean, hyper-text format.
Example
Resources YOUR FEEDBACK
BEA WEBLOGIC LATEST STORIES
SUBSCRIBE TO THE WORLD'S MOST POWERFUL NEWSLETTERS SUBSCRIBE TO OUR RSS FEEDS & GET YOUR SYS-CON NEWS LIVE!
|
SYS-CON FEATURED WHITEPAPERS MOST READ THIS WEEK BREAKING NEWS FROM THE WIRES
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||