Ullrich Hafner

No, I am running latest 4.4.2 and the bug still is there: https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/PR-1075/15/spotbugs/source.011b3afe-630a-44df-8856-41442c138a42/#177

Thanks for starting this PR! In order to finish this PR a couple of more things are required. I will add them to the PR task list.

The Jenkins plugin just visualizes the results of existing tools. It does not itself record the coverage data, this needs to be done by the coverage tools in the build...

From an architectural standpoint, it would make sense to create a new parser for your reports in https://github.com/jenkinsci/coverage-model. Then we simply add a new enum in the code coverage plugin...

> 1. Would you rather me expand the existing CoberturaParser.java to include the additional coverages or keep the formats separate parser files? I think a new parser would make sense....

Yes, the rendering algorithm removes all unknown tags to prevent XSS in the moment. When rewriting the code using the Prism.js source code renderer I need to take care of...

Well, the workspace is exactly the place to write such information to 😄 Interested in providing a PR that uses a temp folder instead?

Actually there is no public API yet, since nobody asked for it up to now. There is a remote API which covers all basic use cases, but no step API....

When there are multiple files specified for one coverage step, then the results of those files are merged. If these files use different module names, then a new tree node...

You are right, it seems that Cobertura does not provide a name for a report in its DTD. So currently I am using "-" as name for each report (and...