This is the first Release Candidate for CruiseControl.NET 1.0 . We gratefully welcome any feedback that can improve the final distribution of 1.0, which we hope to release within the next few weeks.

As always, if upgrading from a previous version make sure to back up your config files, state files, and any build artifacts you care about. We recommend deleting your old install and starting from a clean slate if you can.

Major Changes

There are some big 'top level' changes in this release:

• CCTray has been completely re-written. The version that ships with 1.0 has configuration files that are incompatible with those used by prior releases. In other words, throw away all your old CCTrays, and use the new one. CCTray now ships with its own installer which you can distribute to anyone who wants to monitor your build server.
• The new CCTray has many more features than the old, and is much better for organisations or teams with multiple projects or build servers.
• CruiseControl.NET now has native MSBuild support for .NET 2 . Even if you call MSBuild from a NAnt script rather than CruiseControl.NET directly you'll want to look into using the CruiseControl.NET MSBuild XMLLogger and the MSBuild XSL files.
• The old (single project) web application has been deleted, and CCNet now only ships with the Web Dashboard.
• The main CCNet installer now ships with just the Build Server and Web Dashboard - use the separate CCTray installer for CCTray.
• Integration Properties (passed to NAnt, for example) have been changed to be CamelCased rather than period.separated so you may need to update your build scripts. These properties are now also passed through the <exec> and <msbuild> tasks.

Jira Issues

This is a list of Jira Issues resolved by this release :

Bug

• CCNET-68 - CCTray freezing on network connection problems
• CCNET-92 - CCTray's Popup menu doesn't respond properly when connection fails
• CCNET-119 - CCTray should reload projects after server is restarted
• CCNET-429 - <autoGetSource>true</autoGetSource> for ClearCase
• CCNET-436 - Cvs history command fails if modified directory has been deleted.
• CCNET-450 - There should be sorting on CCTray project list
• CCNET-466 - Support for Source Gear 2.0.6 has broken because it uses the command line "-excludeactions label"
• CCNET-475 - Modifications aren't detected in VSS
• CCNET-480 - NUnit task throws an exception if NUnit output file does not exist
• CCNET-483 - Vault reports "Unable to execute file" error
• CCNET-491 - ccnet.project property passed to NAnt should have meaningful example.
• CCNET-499 - NSIS Install does not default install directory correctly
• CCNET-501 - Create separate install for CCTray
• CCNET-503 - Set app icon for CCTray
• CCNET-505 - Change Integration Properties to be CamelCased rather than period.separated since MSBuild can't handle period.separated property names

New Feature

• CCNET-20 - Support for MSBuild
• CCNET-35 - CCTray should support multiple servers
• CCNET-83 - CCTray should provide notification of build for any monitored project
• CCNET-196 - Pass through more properties to the Builder
• CCNET-317 - Create Failed email notification group
• CCNET-469 - Ability to substitute . for _ on CVS Tag

Task

• CCNET-493 - Delete Web Project (replaced by Dashboard)
• CCNET-494 - Remove Web Service from binary distributions
• CCNET-496 - Replace old CCTray with new CCTrayMulti code
• CCNET-497 - Update CCTray documentation to reflect new CCTrayMulti
• CCNET-498 - Rename IView to IResponse

Improvement

• CCNET-55 - Show Server Version in Dashboard
• CCNET-62 - Refactor QuietPeriod implementation into a separate class
• CCNET-97 - Changes within delay window should cause CCNET to retry again
• CCNET-128 - NUnit task should have configurable timeout
• CCNET-233 - Pass CCNet values to Command Line builds
• CCNET-428 - CVS should convert illegal characters in labels
• CCNET-464 - Publisher collection for a Project should contain the XmlLogger by default
• CCNET-465 - Iteration Labeller
• CCNET-470 - Several Source Control Blocks for one project
• CCNET-472 - Cvs should support getting rebased from Project working directory
• CCNET-476 - Support passing all IntegrationResult properties to ExecTask
• CCNET-477 - Allow User to specify that a MultiSourceControl only returns modifications if all SourceControls return a non-empty list
• CCNET-502 - Exceptions thrown by Dashboard Actions should appear in templated page