Hi James -
Make sure that your tool output is in some kind of xml format.
In the ccnet.config file, modify the publishers section your project
<publishers>
<merge>
<files>
<file>c:\fromcvs\myrepo\myproject\build\test\unit-test-
results.xml</file>
</files>
</merge>
<xmllogger />
</publishers>
I assume you already got this far from what you said.
Next, you need to modify the dashboard.config file - C:\Program Files
(x86)\CruiseControl.NET\webdashboard\dashboard.config, by adding a new
xslFile element to the dashboard/plugins/buildPlugins/
buildReportBuildPlugin/xslFileNames element.
...
<buildPlugins>
<buildReportBuildPlugin>
<xslFileNames>
<xslFile>xsl\header.xsl</xslFile>
<xslFile>xsl\msbuild2ccnet.xsl</xslFile>
<xslFile>xsl\modifications.xsl</xslFile>
<xslFile>xsl\YourCustomTool.xsl</xslFile> <--- this would be
your new line.
</xslFileNames>
</buildReportBuildPlugin>
<buildLogBuildPlugin />
</buildPlugins>
...
that YourCustomTool.xsl (any file name, by the way), goes in this
directory. C:\Program Files (x86)\CruiseControl.NET\webdashboard\xsl
I recommend recycling the application pool you have the CCNET
application running on. I believe it caches the XSL, and possibly even
the transforms.
Let me know if you get any traction out of that! Good luck.
Jeremy
On Oct 6, 12:16 pm, James Wright <[email protected]> wrote:
> I have a couple of web application solutions that we build that
> include a number of JavaScript files. Recently we have had some
> issues where syntax errors in those scripts made it to QA. So being
> the build manager I am I found a nice little tool that checks
> JavaScripts for syntax errors.
>
> I was easily able to integrate the output from this tool into the
> build log for the project, but now I would like to include that output
> into the build report which is something I have not done before and
> I'm looking for some guidence on how I would implement this. Any
> assistance is greatly appreciated. Thanks.
