This page last changed on Jan 16, 2005 by mroberts.

The CruiseControl.NET Server

CruiseControl.NET (CCNet) consists of a suite of applications, but at its core is the CruiseControl.NET Server which is an automated integration server.

The Server automates the integration process by monitoring the team's source control repository directly. Every time a developer commits a new set of modifications, the server will automatically launch an integration build to validate the changes. When the build is complete, the server notifies the developer whether the changes that they committed integrated successfully or not.

Read more about this process at CruiseControl.NET Integration Process.

Effectively, integration becomes as easy as checking in code. Using an automated integration server not only makes integration easy, it also guarantees that an integration build will happen. There is no danger of developers forgetting to validate their changes after checking in.

The CCNet Server offers several key features:
  • Integration with a variety of Source Control systems
  • Integration with other external tools, such as NAnt and Visual Studio
  • Can build multiple projects on one server
  • Remote management and reporting

You can see what applications CruiseControl.NET integrates with at Using CruiseControl.NET with other applications.

CruiseControl.NET Tools

The other applications in the CruiseControl.NET suite are:

  • Web Dashboard: an ASP.NET web application that gives you a status and detailed view of the CruiseControl.NET projects in your organisation
  • CCTray: A client System Tray application that enables you to see 'at a glance' the state of your projects from any machine on your network.

Extra Modules

The following separate modules give extra integration features:
  • Web Service: Proxies the Server's management interface as a web service
Document generated by Confluence on Jun 26, 2005 17:23