Page History

...

These instructions will concentrate on using the Windows installer. The other two options are available if a more customized installation is desired or necessary.
Once the installation file has been downloaded, executing the installer should open a window

Select all the components. Next, the installer will ask for a location. This location should have sufficient rights for read/write

Clicking install will start the installation. After the installation is complete, there should be a folder containing the program contents

Also, if you open the Local Services control panel for the machine, there should be a service named "CruiseControl Service" available that has not been started yet. Go ahead and start the service to start CruiseControl.
CruiseControl ships with a default Java project named ConnectFour. When CruiseControl starts, it will try to build this project (using Ant) and return a result. To see if this has occurred, open the CruiseControl dashboard at the following location: http://<serveraddress_or_localhost>:8080/dashboard||||||||||\. The application dashboard will launch and you should see a screen like below

If the build has passed, then CruiseControl is configured and running properly in its default state.
Some troubleshooting tips if installation does not work:

...

Another change is in the solutionOpen method.  You must add your own FileWatcher license code, available at http://servoy-plugins.de^{Image Removed}

Other changes can be made to the importSolution method to adjust import settings if necessary.

...

At this time, it is a good idea to create the workArea file structure, create a folder name workArea and build the following structure (note that some of the files needed are provided later in this document)  This is where most of the work will occur during the operation.  CruiseControl will be configured to run out of this folder. 

• antscripts
  • test_runner
    • cc_build.xml
    • export_and_test.xml
    • export_and_test.properties
    • servoy.properties
• artifacts
• checkout
  • test_runner
• logs
• config.xml
• cruisecontrol.properties
• dashboard-config.xml

...

cc_build.xml - this file needs to be constructed to actually run unit tests and exports.  Follow the structure for the example and just modify to suit your specific situation.  Keep in mind that it is design to do a unit test and export if any changes occur in any module of the main solution or the resources project.  The example provided shows for two main solutions, a single module for the second solution, and a resources project.

servoy.properties - a separate properties file for any db connections used to run unit tests, as well as a repository for the unit tests.

Step 8 - Restart and force build/commit change

...