UPDATE 6.19.2008 for CC.NET RC 1.4

http://blog.domaindotnet.com/2008/06/19/open-source-project-updated-cruise-controlnet-advanced-metrics/

Continuous Integration as Transparency Mandate

C.I. is far more then simply providing 'build success' of your code. If your not doing more, your not doing C.I. as expected in 2008 and beyond.

The standard is offering all who might care transparency into your software's current state. This means (as an example) architectural metrics in real-time across qualitative and quantitative metrics. And it's now very easy to achieve yet many are not aware of this fact.

This also includes the visual display of how metrics are changing over time (via the attractive graph format you see here as an example).

Abbreviated Statistical Providers

• Microsoft FxCop Statistics
  • All FxCop Data Supported
• NDepend Architectural Metrics
  • Application Level
    • LinesOfCode
    • CommentLines
    • Many more including Number of Namespaces, Types, Methods, & Fields
  • Assembly Level
    • LinesOfCode
    • CommentLines
    • Afferent Coupling (Ca)
    • Efferent coupling (Ce)
    • Relational Cohesion(H)
    • Instability (I)
    • Abstractness (A)
    • Distance from main sequence (D)
  • MUCH more...
• NCoverExplorer from NCover (for understanding how much of your code is covered by unit tests)
  • Code Coverage on Unit Tests and how coverage is getting better, worse or staying the same.
• Many more...

CCStatistics allows you to rebuild your historical statistics information from all your legacy build results. This is critical if you add a new statistic to measure, as by 'out of the box' it will not import any existing information. This solves that issue when the data (via XPat

Background Information

• CruiseControl Statistics
• NOTE: The graphing you see is now part of CC 1.4

Resources

• ClickOnce Deployment Installation to run directly on Build Server
• CruiseControl 1.3
• NMock2 , an excellent Mock Framework (which is an essential element of any C.I. deployment).
• CCNetConfig