You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,7 @@ The Jenkins Coverage Plug-in collects reports of code coverage or mutation cover
17
17
-[JUnit](https://ant.apache.org/manual/Tasks/junitreport.html): Test Results
18
18
-[NUnit](https://nunit.org/): Test Results
19
19
-[XUnit](https://xunit.net/): Test Results
20
+
- Metrics XML report
20
21
21
22
If your coverage tool is not yet supported by the coverage plugin, feel free to provide a pull request for the [Coverage Model](https://github.com/jenkinsci/coverage-model/pulls).
22
23
@@ -113,6 +114,7 @@ The Coverage Plug-in supports the following report formats:
113
114
-[JUnit](https://ant.apache.org/manual/Tasks/junitreport.html): Test Results
114
115
-[NUnit](https://nunit.org/): Test Results
115
116
-[XUnit](https://xunit.net/): Test Results
117
+
- Metrics XML report
116
118
117
119
Some of these report files are generated by other tools and may contain invalid or inconsistent information. By default, the plugin tries to fail fast if such a broken file is detected. You can disable this behavior by setting the property `ignoreParsingErrors` to `true`. In this case, the plugin will try to parse as much information as possible from the report file.
0 commit comments