A good idea, but I'm running afoul of another maven bug when I do that - the site goal is failing with a NullPointerException because of an outstanding maven bug. I could have continuum run the surefire-report:report goal instead, but that only runs properly with -Dmaven.test.skip=true, which would mean I would lose any notification of failed build status. Catch-22. : (
Edwin On 11/20/05, Ralph Pöllath <[EMAIL PROTECTED]> wrote: > > On 19.11.2005, at 07:53, Edwin Park wrote: > > I'm using maven2 with continuum. I'd like to be able to include > > test reports > > in the build results pages, but I don't know how to do this or even > > if this > > is possible with continuum. > > > > All I see right now is the build output, and if I look in the > > targets/surefire-reports subdirectory of the current working copy I > > can see > > the txt and xml versions of the test reports. This is inconvenient > > to look > > through because in order to find out which individual tests have > > failed I am > > forced to open each individual txt report file, plus these reports > > are only > > available for the most recent build attempt. > > > > Right now what I'm doing to generate test reports is to manually > > run 'mvn > > surefire-report:report -Dmaven.test.skip=true' outside of > > continuum. I'd > > much rather have this integrated into the continuum build somehow. > > > > I'm hoping I'm just missing something obvious and turning on test > > reporting > > is easy to do... > > Instead of inspecting the working copy, maybe you could have > continuum run site:deploy as part of the build? > > Cheers, > -Ralph. > > >
