Thanks, Aaron. That was keen observation.
Aaron was right. But I have just committed a change to "build.xml" (please update hackyBuild module):
line 16 changed from <target name="installBuildSensor" if="build.sensor.enabled"> to <target name="installBuildSensor">
This way "build.sensor.enabled" property is no longer used. Only "ENABLE_BUILD_SENSOR" in "sensor.properties" file controls the build sensor behavior.
Cheers,
Cedric
Aaron Kagawa wrote:
I'm fairly certain that Cedric has forgotten to mention that you need to add "build.sensor.enabled=true" to the hackystat.properties file if you want to send data.
When this property is enabled along with all the others that Cedric mentioned. You should be sending Build data that looks somewhat similar to the following:
#> Build [add, , , , <BuildReport><BuildContext StartTimeMillis="1107573528059" EndTimeMillis="1107573923047" Project="hacky2004-all" Configuration="Unknown" StartType="Unknown" /><BuildResult BuildFailed="false" CheckstyleRunned="false" CompilationRunned="true" UnittestRunned="false" /></BuildReport>]
Cedric: having a XML data field is a great idea. its much more robust than the comma separated values.
thanks, aaron
At 04:27 PM 2/4/2005 -1000, you wrote:
Hi,
When you check out the latest version of hackyBuild, you would find that build fails. Please update two jar files, and copy/overwrite them to your global ant lib directory.
Files to copy/update: (1) hackyBuild/lib/ant/sensorshell.jar (2) hackyBuild/lib/ant/sensor.build.jar
(Note that "ant updateAntLib" may not do the trick.)
I would also like to ask everybody in CSDL to do me a favor to enable the build sensor on your workstations/laptops.
To enable the sensor, please follow the following instructions:
(1) Make sure "ENABLE_BUILD_SENSOR=true" exists in "Sensor.properties files".
(2) Make sure "ProjectID=hacky2004-all" exists in "hackystat.properties" file.
Thank you, and your help is greatly appreciated.
Cedric
