I’ve previously only been looking at adding non-commercial modules to ASL, because it makes it very easy for me to distribute an “all-in-one” download. However, it certainly wouldn’t be too hard to add a module to integrate Clover, with instructions on how to configure it.

I might get in contact later to discuss how to add it in to ASL. It will probably be much later, though, as I have some deadlines over the next few weeks and months (not to mention CITCON!)

The upcoming release of Clover 2.6.0 may be interest to you. It includes an API to allow Clover to be integrated into any Ant build – the javadocs are already online here: http://docs.atlassian.com/atlassian-clover/

Alternatively, you can integrate Clover into an Ant build with about 3 lines of Ant XML: http://confluence.atlassian.com/display/CLOVER/Clover-for-Ant+Two+Line+Integration
This will also generate clover history points, and historical reports to allow trend-reporting – something very valuable when viewing Code Coverage data.

If you would like any help getting Clover integrated with the ASL, please let me know!

Cheers,
Nick Pellow
Atlassian – Clover

The message of our Build Engineer Bootcamp was that build scripts need to be treated more like code. Douglas Bullard has some really excellent slides on Object Oriented Ant Scripts that show how to take common OO concepts and apply them in Ant. But ……

To me, it makes sense that CI products are well placed to present trends in a coherent manner, because they are in charge of the invoking build after each change. They inherently know the time based aspects of the code.

However, I don’t regard trending as a CI only exercise: I believe it should be part of a good automated build to give access to this. One day I’ll get it into ASL (perhaps!)

You make a really good point on the importance of trends over time. I got used to taking that for granted while I was Agitar with our Dashboard, and now that I’m at Urbancode trending is built into AnthillPro as well. But there’s something about build tools that seems oriented to points in time rather than trends. No idea why…