So it looks like the logging was still the problem. I was not seeing the compile errors for a project when I used <exec> for devenv.exe. I changed this to the <devenv> task and I also stopped merging any msbuild and nunit logs as these were appearing twice in the output.
I'm starting to like CCnet... just a little... :) On Fri, Aug 5, 2011 at 3:51 AM, Philip Sayers <[email protected]> wrote: > Check how long the build is taking and compare to your timeout settings (or > the default timeout). > > In older versions of ccnet (1.4.x I think), a build taking longer than the > timeout setting can cause a build failure with no indicating in the build > log about the timeout. Server log contained the 'failed due to timeout' > information though. > I'm not sure is this is still the case in your ccnet version. > > If you're not seeing a failure from the 'compile' step (msbuild). > Something > in one of the other steps is causing it. > > Phil > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Peter Jones > Sent: Wednesday, August 03, 2011 4:20 PM > To: [email protected] > Subject: Re: [ccnet-user] Re: CCnet dont parse log files :( > > Ah, I figured it out. The msbuild plugin was missing from the dashboard > config. Now I just need to figure out why the build says it's failed when > the log says it hasnt. > > Cheers > > On Thu, Aug 4, 2011 at 8:07 AM, Peter Jones <[email protected]> wrote: > Hmm, yes, that is very likely. Is there a sample of this somewhere? > > Thanks > > On Thu, Aug 4, 2011 at 3:52 AM, JayFleming <[email protected]> > wrote: > Is it possible that you haven't plugged the relevant XSLs into your > dashboard/email config? > See: http://confluence.public.thoughtworks.org/display/CCNET/XSL+Files > > Cheers, > Jay > > > >
