For a long time now, our Cruise Control .NET dashboard is inconsistently generating NAnt outputs and timings reports.  Sometimes, it was generated, sometimes a message of "Please make sure that NAnt is executed using the XmlLogger (use the argument: -logger:NAnt.Core.XmlLogger).".  But the docs says when a Nant task was executed by CruiseControl, it automatically uses such logger if none was specified (as was our configuration).

I found out last friday that NAnt 0.85 was officially released last October 14 (How come i did not see that from my tech newsletters).  We were still using 0.85 RC2 on our project and when i browsed the Release notes, the said bug on the xmllogger was fixed on RC4.  Now it's a breeze knowing what caused a failed build on our continuous integration server.  
For the past weeks now, my coding has been disturbed by broken builds since i am the one maintaining it.  All along i thought i was the one who broke the said reports when i shifted our testing framework from NUnit to MbUnit.

---

Posted 10-23-2006 1:01 PM by jokiz