I would recommend using a custom xsl in the buildReports that makes use of xsl:include. See the following references http://homepages.ius.edu/rwisman/A346/html/xslInclude.htm http://www.dpawson.co.uk/xsl/sect2/N4760.html
On Sep 16, 12:53 pm, Daniel Hommel <[email protected]> wrote: > Hi all, > > i have a growing number of tools in my process that don't offer options > to output XML, but a lot of them can generate HTML reports. Is there a > good way to integrate those reports in the dashboard? > > A working solution would be to copy the reports to a directory that is > accessible through the same webserver as the dashboard using the exec > task or NAnt or else, and add some XSL hacks to link to the directory > for each build. > > Would it be a good idea to create a task to publish HTML reports to a > certain directory (artifacts directory?) and output some XML that > contains links to the published reports and arbitrary additional > information (tool name etc) to the build log. That way it would only > need one simple XSL sheet to handle all tools that only offer HTML > reports once and for all. Or do you consider this overkill? > > Thanks for sharing your thoughts. > > Kind regards, > > Daniel
