CruiseControl.NET
Get flash to fully experience Pearltrees
After years of good collaboration with Thoughtworks, it appeared that Thoughtworks had less resources to spent for CCNet. This problem came painfully visible when their site was hacked with a virus. It took a long time for the help page to come back up, and the build server is still not up. Some months ago we (the active members) decided to move the hosting to another server, so we would be less dependent on Thoughtworks. No hard feelings, it were great years of cooperation but time moved on.
CruiseControl.NET
The idea here is that we add child pages for each significant alternative with an assessment of what people like and don't like about the other tool. Any interesting similarities and differences should also be added.
Alternatives
Feature matrix
Note: : This is starting as a straight copy of the document at codehaus since that word is that it will be archived (see comments on the page at codehaus). There are many Continuous Integration systems available. This page is an attempt to keep an unbiased comparison of as many as possible of them. The goals are: The feature existsSourceMonitor
SourceMonitor Version 3.2 The freeware program SourceMonitor lets you see inside your software source code to find out how much code you have and to identify the relative complexity of your modules. For example, you can use SourceMonitor to identify the code that is most likely to contain defects and thus warrants formal review.
CruiseControl.NET (ccnet) includes style sheets and integration instructions for Vil - a static analysis tool that provides a whole bunch of metrics for your code such as cycolmatic complexity , lines of code, number of methods, etc all of which are useful in monitoring the health of your application.
Integrating CruiseControl.NET & SourceMonitor
SourceMonitor and CruiseControl - The Top 15
As a follow up to yesterdays post on SourceMonitor and CruiseControl.NET integration , Eden Ridgway has done some really nice work and posted a few styles sheets to help you create a SourceMonitor Top 15 Summary of worst methods so you can target your refactoring efforts.
