The trunk user doc build has six warnings, yet the build succeeds. Warnings indicate formatting errors. Should the user doc Hudson fail on warnings, as that is what it is there to detect?
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Hey. .
I'm not sure if anyone responded, but I wager that Hudson would always fail if we waited for the docs to have no formatting warnings.
Don't get me wrong, I'm not advocating for warnings, but they seem to be only slightly less common then spelling mistakes. Right now, however, there are a couple of new sections that haven't been connected to the table of contents and one warning that I have yet to resolve but doesn't effect the display. Mike and I were going to look at the latter sometime this week. As for the former, I am not sure who added the 2 sections--I fear svn blame--but my intention was to look through them, edit, and then add to the table of contents. Since this sort of review takes a while and these sort of warning doesn't effect the web display, I've let the warnings hang on. This doesn't seem to be the ideal way of doing things, so if there's a better way, let me know.
Best,
Alyssa.
Ben Caradoc-Davies wrote:
The trunk user doc build has six warnings, yet the build succeeds. Warnings indicate formatting errors. Should the user doc Hudson fail on warnings, as that is what it is there to detect?