Hi there

I’m making Cruise do CI for a .NET-based product. One of the jobs is to run code-coverage, using NCover. Now; we only have a license for the CI server, not for individual developers. This means that the CI server is the only place developers can go to to pull down coverage reports – in NCover’s case, this includes the summary for the product at the module/type level, and the detailed report that will actually highlight which lines of code are covered/not-covered.

Unfortunately, the detailed report consists of thousands of small files, one per source file (I guess), one per namespace-module, and a few more on top. This means that opening up the artifacts tree in the stage/job details page is SLOW – mine is 7Mb.

This is because that page is not lazy-loading the tree of artifacts; this is happening on the server-side, as opposed to via AJAX requests, one per node-expansion.

This means that to even open the page to see the summary report, I need to wait for 7Mb of data to come down the wire. This is too long, I’m afraid; people won’t wait long enough, and as a result, our code will go uncovered because it simply takes too much effort to look at the report :-(

Please can this be improved?

Hey Pete

I can see how this would be a pain. Once upon a time, this was done via AJAX—but we binned this because the latency was annoying.

There is a workaround—create a tab from the summary report: http://studios.thoughtworks.com/cruise-continuous-integration/1.0/help/cruise_integration.html (see “integrating artifacts in tabs”).

Meanwhile we’ll look at fixing this.

Jez.