Hosted By:
SourceForge

Cruisecontrol
Configuration


 

Overview

All building/deployment is done using apache ant. You must have ant installed and available via the command line or your IDE.

Building Application

The application may built several different ways. These include: a standalone java application, a dynamic webstart application that can be deployed in any J2EE web compliant container, and a static webstart deployment which may be used from a stanalone web server like apache. The application may also be built and run from your IDE using the SystemStartup class as the main class.

Standalone Application

The standalone application may be built using the build.standalone.dist ant target (optionally, you may run the clean target to clean the file contents before running the standalone target). This will create a dist directory that contains standalone.zip file containing a standalone version of the application. Additionally, there will be a configuration directory under the dist directory containing the unzipped contents. The bin directory contains a startup.bat and startup.sh script that will run the standalone application.

Dynamic Web Application

The dynamic web application may be built using the build.webstart.dist ant target. This will create a dist directory that contains cc-conf.war file containing a web application. This war file may be dropped into any J2EE compliant web container. The url for the application is http://yourwebserver/cc-config/cruisecontrol-gui.jnlp.

Static Web Application

The static web application may be deployed in a standard web server such as apache and may be built using the build.static.webstart.dist ant target. This will create a dist directory that contains configuration.zip file containing a webstart enabled version of the application that may be unzipped into the root directory of a standard web container.