There is a comparison chart that shows the differences between various CI servers at http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix. It appears to be reasonably up to date, although CC.Net is about to roll-out a heap of new features in the near future.
As a quick summary, CC.Net is an open-source project that is based on the .NET 2.0 framework. It has three components - the server, a web dashboard and a windows-based monitoring app (CCTray). It uses a text- based configuration file (needs to be modified by hand). It does not support distributed builds (yet) and has no security (coming in the next version). Cruise is a commerical application, built from the ground up in java. Again it has a server component and a dashboard, not sure about a windows-based monitoring app. The configuration can be modified within their dashboard (not sure how it is stored), does support distributed builds and has security. CC.Net is supported by TW, but they don't actively provide code for it (there is only TW worker on the active dev list). Cruise is actively developed by TW (and only TW). Hope this helps - we'd love you to stick with CC.Net of course ;-) Craig On Mar 6, 11:20 am, SMS <[email protected]> wrote: > Hello, > > I have been using CCNET for more than 3 years now. I have been pretty > satisfied with how it works. > I just got to know about from Cruise (again by ThoughtWorks). > What is the exact difference between these two products? > Why should I stick to CCNet when Cruise has come out in market? > > I need some substantial answers since I got answer to my c-workers who > have been insisting that we should start using Cruise instead of > CCNet. > > Thanks.
