-
Bug
-
Resolution: Fixed
-
Major
-
None
-
jenkins 2.65, performance plugin 3.1
Since at least version 3.1, relativeFailedThreshold and relativeUnstableThreshold appear to be failing builds or making them unstable if the number of failed builds exceeds or varies by the value set, rather than if the response time varied by those amounts.
07:54:24 Performance: Percentage of errors greater or equal than 0% sets the build as unstable 07:54:24 Performance: Percentage of errors greater or equal than 0% sets the build as failure 07:54:24 Performance: File abcJunit.xml reported 0.0% of errors [SUCCESS]. Build status is: UNSTABLE 07:54:24 Performance: File xyzJunit.xml reported 4.0% of errors [FAILURE]. Build status is: FAILURE
Our servers running V2.0 don't behave this way, obviously, and the same builds of the same code don't fail there.
14:02:30 Performance: Percentage of errors greater or equal than 0% sets the build as unstable 14:02:30 Performance: Percentage of errors greater or equal than 0% sets the build as failure
I've never understood what this output means, either, and the value is always 0%, which seems improbable but at least it doesn't fail builds.
Pipeline settings:
performanceReport compareBuildPrevious: true, configType: 'ART', modeOfThreshold: false, modePerformancePerTestCase: true, parsers: [[$class: 'JUnitParser', glob: '**/*Junit.xml, **/TEST-*.xml']], relativeFailedThresholdNegative: 0.02, relativeFailedThresholdPositive: 0.02, relativeUnstableThresholdNegative: 0.01, relativeUnstableThresholdPositive: 0.01
We really need some proper, clear explanations and examples of how this plugin is supposed to work as the docs are still not clear to me, today.
