4

I am interested to publish jmeter report in Jenkins and set the pipeline as "failed" if there are degradation in terms of performances between the previous executions.

Below the configuration set in my Jenkinsfile for my jmeter results:

                perfReport filterRegex: '',
                        relativeFailedThresholdNegative: 0,
                        relativeFailedThresholdPositive: 0,
                        relativeUnstableThresholdNegative: 0,
                        relativeUnstableThresholdPositive: 0,
                        sourceDataFiles: 'resultsJmeter/output/*.xml'
                    }

Is there any way to evaluate automatically the previous executions (if any) ?

Prisco
  • 653
  • 1
  • 15
  • 30

1 Answers1

4

As per Performance Trend Reporting article:

You can configure the error percentage thresholds and the relative percentage thresholds which would make the project unstable or failed or set them to -1 to disable the feature

As per How to Use the Jenkins Performance Plugin

enter image description here

Set the following values:

Unstable: 10
Failed: 60

This configuration will mark the build as unstable when errors are at 10% and as failed when 60% of our requests failed.

The relevant pipeline syntax would be:

perfReport errorFailedThreshold: 60, errorUnstableThreshold: 10, filterRegex: '', sourceDataFiles: 'resultsJmeter/output/*.xml'

for the relative to the previous build: 

perfReport relativeFailedThresholdNegative: 10, relativeFailedThresholdPositive: 60, relativeUnstableThresholdNegative: 5, relativeUnstableThresholdPositive: 30, sourceDataFiles: 'resultsJmeter/output/*.xml', filterRegex: ''
Dmitri T
  • 159,985
  • 5
  • 83
  • 133
  • 1
    is it checking also degradation in terms of time? I mean, if a rest api in my previous changes took 10ms and after some changes it takes 10s, is it forced to fail? – Prisco Feb 17 '20 at 14:59