-
New Feature
-
Resolution: Fixed
-
Major
-
None
Since 2.x the official supported JUnit report schemas are the most used in Java world (ant and maven surefire).
The breaking changes was introduce (since 2.x using semantic versioning), a warning is shown in the Jenkins plugin page and all details provided in the Wiki page
To provide supports for the who use tools which declare to produce a JUnit report that is not strict to any official schema, the procedure is configure the xUnit plugin select the "Custom Tool" as test type and provide the path to a custom XSL (it will be provided by this plugin as attachment and documented in Wiki page) in the "custom stylesheet" textbox. The path of the XSL file that can be absolute on the server (jenkins master) or relative to the workspace or an URL (see the wiki page for more details).
The XSL is free and could be customised to fit every extra needs.
- depends on
-
JENKINS-32920 Support for URL for stylesheet in Custom Tool
- Resolved
- is related to
-
JENKINS-51920 jUnit output of pytest/Selenium test fail to parse
- Closed
-
JENKINS-53115 Failure to parse JUnit after upgrading from 1.104 to 2.2.3
- Closed
-
JENKINS-52152 xunit cannot read junit time attributes with more than three decimals or using exponential notation
- Closed
-
JENKINS-51914 junit output of nosetests fails to parse
- Closed
-
JENKINS-51919 jUnit output of PHPUnit test fail to parse
- Closed
-
JENKINS-28000 xUnit not testing against the appropriate XSD?
- Closed
-
JENKINS-57615 xUnit fails to parse PHPUnit output when a skipped test also has system output
- Closed