Hi!
If there is a broken build, informations about the reason can be found
in two files:
* the workspace log, which can be found in the logs directory of the
nightly build download site (http://download.rubypeople.org/nightly/)
* the "Xml log file" on the cruise control build results page
(http://213.239.199.113:8080/cruisecontrol/buildresults/RDT). If this
file is large the browser might hang. In that case you can download the
log file with "Save Link as..". With verbose ANT this file is about 10
MB large, without it is about 700kb.
Please mind that the cruise control build result page can need quite a
lot of time to display if it is called the first time after a build.
That is because xsl transformations have to take place. I couldn't find
a way to run the transformations directly after the build has finished.
Markus
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Rubyeclipse-development mailing list
Rubyeclipse-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
