-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Jenkins v1.605
performance-plugin v1.13
Windows Server 2008 R2 Standard
We recently updated our performance-plugin from version 1.9 to 1.13, and noticed a regression: no matter how many JMeter samplers report an error, the job is never marked as failed.
Please find attached a screenshot of our configuration, and a JMeter *.jtl report to test this with.
With version 1.9 of performance-plugin, we get the following output:
Started by user anonymous Building in workspace D:\jtls Performance: Percentage of errors greater or equal than 0% sets the build as unstable Performance: Percentage of errors greater or equal than 0% sets the build as failure Performance: Recording JMeter reports '*.jtl' Performance: Parsing JMeter report file should_fail.jtl Performance: File should_fail.jtl reported 100.0% of errors [FAILURE]. Build status is: FAILURE Build step 'Publish Performance test result report' changed build result to FAILURE Finished: FAILURE
With version 1.13, this is the output:
Started by user anonymous Building in workspace D:\jtls Performance: Percentage of errors greater or equal than 0% sets the build as unstable Performance: Percentage of errors greater or equal than 0% sets the build as failure Performance: Recording JMeter reports '*.jtl' Performance: Parsing JMeter report file 'C:\Users\Stefan.Zwanenburg\.jenkins\jobs\test-performance\builds\3\performance-reports\JMeter\should_fail.jtl'. Finished: SUCCESS
