Note: Just uploaded document, need to go through and fix anything that did not convert correctly.

Building a Software Factory

...

• A unified code repository - – the team must have access to shared code (team sharing, SVN)
• Daily commits - – every developer commits daily to the repository so changes are incremental
• Commits are built - – when the code is committed by a developer, the software is built to show it is functional.
• Builds are automatically tested - – When the code is built, unit tests are performed, so if errors are found in a unit test, the developer can correct those errors immediately.
• Results are available to everyone - – if a build breaks, everyone can see where the issue lies and what needs to be done to fix it.
• Successful builds are deployed immediately (automated deployment) - – this ensures that the latest software is available to everyone in the team (product owners, testers)

...

• Repository software - software to manage the code base (SVN)
• Build software - – software to actually build and run unit testing (ANT)
• Communication software - – how to communicate information among the team members.
• Deployment software - – in our case, Servoy Application Server.
• Continuous build software - – software to manage the continuous build process and make sure each step is occurring.

...

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:

...