-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
- Ubuntu 32 bit, OpenJDK 1.6.0_22
- Jenkins 1.410 from the Jenkins debian repo
- Performance plugin 1.6 installed trough the web interface
- Standard maven project (created with archetype:quickstart) with one unit test
- For the build I've configured the performance plugin with one junit entry and set the "Report files" directory to "target/surefire-reports"- Ubuntu 32 bit, OpenJDK 1.6.0_22 - Jenkins 1.410 from the Jenkins debian repo - Performance plugin 1.6 installed trough the web interface - Standard maven project (created with archetype:quickstart) with one unit test - For the build I've configured the performance plugin with one junit entry and set the "Report files" directory to "target/surefire-reports"
The performance plugin doesn't parse the JUnit reports correctly (it uses the JMeter parser for them). This can be fixed by harcoding JUnitParser instead of JMeterParser in PerformanceReportMap, so that it looks like the following (around lines 62-63):
if (files != null)
{ addAll(new JUnitParser("").parse(buildAction.getBuild(), Arrays.asList(files), listener)); }However a better fix is needed which selects the appropriate parser based on the current configuration.
- is related to
-
JENKINS-5571 PLUGIN: Performance - Graphs and Statistics of TestRuns based on JUnit File Shown in Uncorrect Way
- Resolved