.NET Cruise Control Builds Failed Time

Question

My team aims to minimize the time during which our assembly is broken.

We use CruiseControl.NET for continuous integration. I would like to know what is the best approach to answer the following question:

"In the last {timespan}, how much time has passed {project-name} in a broken state?"

For example: "Over the past 1 month, how much time did our project spend on violating the status?"

Are there any additional CruiseControl.NET features that would make it easier to provide this information in some type of report or somewhere in the control panel?

Alternatively, how do you approach parsing xml artifact files to get this information?

Answer 1

I see at least two ways to approach this:

• You write an external tool that parses the CC.NET XML log files for the project (stored by default in the buildlogs subdirectory), calculates statistics, and writes an HTML report. This is probably easier to do, but it will not be directly integrated with CC.NET.
• For this, you are writing a CC.NET plugin . In this case, you will need to investigate a little. I assume the starting point would be to look at the source code of some existing plugin.

Here are some links about CCNET plugins:

• http://www.cruisecontrolnet.org/projects/ccnet/wiki/DevInfo_MakingPlugins
• BrekiLabeller is my own plugin, useful if you want to see how a plug-in can be implemented.

Answer 2

you can use the statistics publisher, http://www.cruisecontrolnet.org/projects/ccnet/wiki/Statistics_Publisher and you can display them through the project statistics plugin

Answer 3

Looking very quickly at the CC docs, I assume that if you wrote your own cruise control dashboard, you could use the RSS feed for the build results, analyze all the time dates and success / failure status to your threshold value, then summarize the totals.

Regarding the dashboard display, I think Cruise Control has a plugin architecture that can help http://cruisecontrol.sourceforge.net/main/plugins.html

Answer 4

So my possible solution was not perfect, but it was easy to do, and it works:

I sent CC.NET a mailing list to the email address (we will call it build_emails@build_statistics.com). Then I use ruby ​​script to receive emails via imap and process them to determine build failure time.

I did not follow the path of parsing xml directly, because I would have to parse each xml file in a timeframe to create a timeline, and then go to the timeline to complete my calculations. It seemed too difficult to get simple statistics like this.

Answer 5

I like cc.net, but in this case TeamCity just does it for you. He has many other excellent statistics. It is free for less than 20 projects.