- Download the installation package from Sourceforge.net.
- Run the installer. This will copy the files you need and create the IIS site/virtual directories needed to access Cruise Control .NET from your browser.
- Open your Internet Information Services (IIS) Manager (Start -> Run -> inetmgr )
- Create a new website point the site to <INSTALL PATH>webdashboard.
- Change the bindings for the new site to a unique port. ( I use port 90 and the CCNET is then accessed via http://localhost:90)
- Open the application pool created for this site and change the ‘Managed pipeline mode’ to ‘Integrated’.
- Open the services manager (Start -> Run -> services.msc) and start the Cruise Control .NET service.
Security& Permissions Issues
The default installation may cause issues due to permissions required to create folder (there are folders created on the fly for each CCNET project). It is best practice to have the CruiseControl.NET service running under a service account with proper permissions in the <INSTALL PATH>server and <INSTALL PATH>webdashboard directories and subdirectories. The service account needs enough permissions to create new folders and files within the .server folder.
The new version of Cruise Control .NET has an admin dashboard that allows you to manage the plugins to display on the report pages. To enable the login, you need to modify /webdashboard/dashboard.config and add a password for the <administrationPlugin /> element.
As you install and uninstall the plugins, click the View Log button that appears next to the “Package has been installed” message to view the log of the installation. If there were any complications with the installation (usually permissions related), this log is your best source of information).
Visual Studio 2010 Unit Tests
The Visual Studio 2010 unit test results file has changed slightly from 2008. CCNET 1.6 addresses this issue.