Thank you for the reply.
Those were my initial thoughts also. I've double checked and the "JUnit" type is selected in the build configuration section (under "Publish Performance test result report"). I've also compared my .xml report files with the ones from the unit test (in fact I've created a unit-test which drops the same file present in the performance plugin unit-test in the folder parsed by the plugin and got the same result).
I've also checked the logs and it says that the files were parsed successfully (except the .txt file which I'm not interested in):
Performance: Parsing JMeter report file
TEST-com.blogspot.hypefree.AppTest.xml
Performance: Parsing JMeter report file TEST-JUnitResults.xml
Performance: Parsing JMeter report file com.blogspot.hypefree.AppTest.txt
Performance: Failed to parse /var/lib/jenkins/.jenkins/jobs/testY/builds/2011-05-09_17-37-38/performance-reports/com.blogspot.hypefree.AppTest.txt: Content is not allowed in prolog.
I suspect that the problem is around the following lines of the PerformanceReportMap class (this is from the constructor, around lines 62-63):
if (files != null) {
addAll(new JMeterParser("").parse(buildAction.getBuild(),
Arrays.asList(files), listener));
}
I think that JMeterParser shouldn't be hardcoded here, but rather the appropriate parser should be identified based on the
configuration (JUnitParser in this case), however I don't have the necessary expertise with the codebase to implement a fix.
Could you please confirm that this is indeed the issue? If so, I'm happy to log an issue on JIRA, but I don't want to pollute it if the problem is between the chair and keyboard ;-)
Best regards,
Attila Balazs