At 09:17 AM 2/28/2006, Philip wrote:
(1) XmlData provides an easy way to generate Build sensor data from
the Ant log files. Write an XSL transform file, and use the <style>
task in Ant to input the ant build log file and output XML
containing the Build results you want to send to Hackystat.
(2) Don't necessarily give up on the Ant sensor. Let us know what
problems you're having. Maybe it would be easier for us to fix it
than for you to write your own.
The XSL transformation might be an option because I do have a bunch
of archived Ant log files. But, I just think that a "real" Ant log
translator might be more useful.
This seems like a perfectly reasonable way to introduce Hackystat
into an organization without creating the fear of Big Brother. In
fact, you may have stumbled upon a "best practice" for Hackystat
technology adoption. :-)
Yeah, I agree. This might work out pretty good.
It seems to me the DailyProjectUnitTest does more good than harm.
:-) What it computes and caches is precisely what you want: the
total number of unit tests run, passed, and failed. There's
basically no meaningful overhead incurred by its ability to manage
multiple users in a project.
Well, in a single account setting, I would want to know how many
tests were run during the last build (in addition to what
it currently provides). In other words, I would want snapshot and
aggregate unit test data.
That's interesting that the developers run CruiseControl targets locally.
Well, the CruiseControl target doesn't have much more than our regular target.
I agree that the TCC is a "first class interface" to Hackystat, and
although it's already available in several configurations, it is
currently an undocumented feature. We will document it in the near
future via a docbook chapter in the hackyApp_TelemetryControlCenter
module that will show up in the User Guide (or maybe the
Administrator Guide?) for configurations including this module. The
chapter will explain how to install the TCC (with a link to the .jar
file in the download directory of the server), how to write TCC XML
files, and some samples.
Cedric has been desperately wanting to write this chapter, but I've
been making him wait until I finished documenting how to write
docbook documentation. :-)
In addition, it would be useful for me to be able to run the TCC via
Ant and have TCC download the Charts that I've configured it to get.
Once you're at that point, then you can show them your _own_
personal data and how you are using it to help manage your own
personal productivity and quality. Then, maybe just one developer
will want to take the plunge. If so, you're on your way.
Sounds like a plan.
