Hi sounds like a nice addition, but if those tools output HTML, how would one incorporate that into an existing page? --> the page to include will probably also start with <HTML> and maybe headers, not to mention pictures inside those pages.
it would be nice if i worked, but how to get it to work ... I think Craig already had something like this, but I do not know if it is in the trunk, or even in the branch remember : the build server is not always on the same machine as the webDashboard with kind regards Ruben Willems On Thu, Sep 16, 2010 at 8: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 > >
