Hi
there are a few options :
° if you can 'massage' those logs into xml, even simple xml, you could use
a simple xsl to extract them
via configuration in nlog, or pre-preocess the file before merging
° if not possible, you'll have to create an xsl file that works with CDATA
sections, which is not that fun
with kind regards
Ruben Willems
On 23 May 2013 20:46, Todd Bradley <[email protected]> wrote:
> Hi, I just got my first CruiseControl.NET server running. But one thing I
> could not figure out – and found zero helpful information via google about
> – is how to get my build report to include console output from my NUnit
> tests in my build report. We’re using log4net in our test code to give us
> better logging as tests are running.
>
> But that console output seems to go into the bit bucket. So I changed my
> log4net configuration to log to a test file, and then did a merge in my
> <publishers> section to merge that file into the output. But since it’s
> just regular text (not XML), the XSLTs all ignore that output and it
> doesn’t appear on the main build report screen. I can see the output is
> there when I click on “View Build Log”, but I’d really like the log4net
> output to appear as part of the Build Report.
>
> Any ideas? Oh, FWIW, I’m using NUnit directly from CC.NET, not via nant.
>
>
> Cheers,
> Todd.
>
> ****
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "ccnet-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
---
You received this message because you are subscribed to the Google Groups
"ccnet-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
