jason - 28/Jun/07 03:16 AM Hi Angus, Thanks for the feedback. Currently, you are able to hook in HTML reports as artifacts that you can browse from the artifacts tab for the build. To capture an HTML report, use a directory artifact: http://confluence.zutubi.com/display/pulse0102/Project+Directory+Artifacts Pulse will automatically recognise the captured files as an HTML report and link to the report for easy browsing. Beyond this, we are looking at two further things in the Pulse 2.x time frame: 1) Allowing reports to be brought up to a higher level, so you do not need to dig into the build > artifacts tab to find them. This will be configurable, as not all reports will be important enough to warrant this. As part of this work we are also considering allowing custom reports to be embedded directly in the Pulse UI (like the test results) rather than as a separate report. 2) Allowing post-processors to be plugged-in. This means you will be able to write a plugin to process reports for any tool you wish. In the first release, plugged-in processors will be able to add features (errors/warnings) and test results to the build result. Further on, we anticipate that they could be combined with the custom report functionality discussed in 1).

Daniel Ostermeier - 11/Dec/08 05:48 AM Trying to clean things up a little. We currently have a couple of very large buckets of tasks that are really not indications of our scheduling. What I am doing is for starters, moving all of the 2.x. items into x.x to indicate that they have not been scheduled. We can later go through these and pick up with ones that we intend to complete for an upcoming release.