Checkstyle error (line longer than 100 characters) in hackyTelemetry!
Someone is not doing their 'freshStart' before committing :-)
A process-level question: should we add the checkstyle target into quickStart to try to reduce the number of commits with checkstyle errors getting into the daily build? Or are people simply editing the file and immediately committing it, which would mean quickStart wouldn't catch it either. Or, is the frequency of build failures due to checkstyle errors low enough that we shouldn't worry about it?
It would be nice, of course, to have a build report that shows us the frequency of daily build failures over time, and broken down by failure type, and broken down by the top-level module that fails. That would help us figure out what we might want to change in our process, if anything.
Cheers, Philip
--On Wednesday, October 13, 2004 2:02 AM -1000 [EMAIL PROTECTED] wrote:
Hackystat build (configuration Hackystat-UH) failed. Build report is available at http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?year =2004&month=10&day=13&configuration=Hackystat-UH Build Time Stamp: Wed Oct 13 02:02:38 HST 2004
