Artem Fedorov added a comment - 2018-10-22 09:53 Sure. It looks like comparison between 55 and 56 build.   Could you add performance trend for 55 build? And I want to know build statuses for builds 53-56 

Liu Wang added a comment - 2018-10-22 10:02 Artem Fedorov I didn't find performance trend for 55 build, I attached the performance report of 55 build and the performance trend of this pipeline. Is there any information I need to provide?

Artem Fedorov added a comment - 2018-10-22 10:09  This image contains build 56 info.. Also could you please add Console log for 55 build and Build History (from main job page) for 53-56 builds

Liu Wang added a comment - 2018-10-22 10:21 55 build is also compared with 53 build, but performance report shows it always comparing with the previous build(#54) based on Average response time. Although the build of 54 is aborted.

Artem Fedorov added a comment - 2018-10-22 10:26 Sure Could you add the last lines from Console log for 53 and 55 build?  E.g.:  The label "Dummy" caused the build to fail Build step 'Publish Performance test result report' changed build result to FAILURE Also it will be useful if you add config for Performance Publisher step 

Liu Wang added a comment - 2018-10-22 10:37 if (env.COMPARED_NUMBER == '') { echo "Compare with Previous Successful Number " perfReport compareBuildPrevious: true , modeOfThreshold: true , percentiles: '0,50,90,100' , relativeFailedThresholdNegative: 20.0, relativeFailedThresholdPositive: 15.0, relativeUnstableThresholdNegative: 10.0, relativeUnstableThresholdPositive: 10.0, sourceDataFiles: 'independence-solution-loadtests-' +version+ '.' +buildNum+ '/report/result.jtl' } else { echo "Compare with Specific Number ${env.COMPARED_NUMBER}" def compareNum = sh(script: "echo ${env.COMPARED_NUMBER}" , returnStdout: true ).toInteger() perfReport modeOfThreshold: true , nthBuildNumber: compareNum, percentiles: '0,50,90,100' , relativeFailedThresholdNegative: 20.0, relativeFailedThresholdPositive: 15.0, relativeUnstableThresholdNegative: 10.0, relativeUnstableThresholdPositive: 10.0, sourceDataFiles: 'independence-solution-loadtests-' +version+ '.' +buildNum+ '/report/result.jtl' } echo currentBuild.result if (currentBuild.result == 'UNSTABLE' || currentBuild.result == 'FAILURE' ) { emailext body: '${JELLY_SCRIPT, template= "html-with-health-and-console" }' , subject: "Build failed: ${env.JOB_NAME}" , to: '${DEFAULT_RECIPIENTS}' , replyTo: 'no-reply@kingland.com' , mimeType: 'text/html' ; } I added the codes that configuration of performance report in jenkinsfile.

Artem Fedorov added a comment - 2018-10-22 15:13 OK Will try to fix it on this week

Liu Wang added a comment - 2018-10-23 01:35 Thank you very much for your help, looking forward to your good news.

Liu Wang added a comment - 2018-10-31 01:43 Hi Artem Fedorov , Is there any update for this issue?

Artem Fedorov added a comment - 2018-10-31 08:19 Hi Liu Wang   I working on this issue now. I hope that I'll finished it today/tomorrow 

Artem Fedorov added a comment - 2018-11-01 09:06 Hi Liu Wang In version 3.13 we added `Baseline build` option in Advanced options. If this value is empty or 0 - all Performance trends will be compare with previous build, if not 0 then Performance Trend will have comparison with selected build https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/performance/3%EF%BF%BD%EF%BF%BD.13/performance-3%EF%BF%BD%EF%BF%BD.13.hpi  

Artem Fedorov added a comment - 2018-11-01 09:07 fixed in 3.13

Liu Wang added a comment - 2018-11-02 00:26 Artem Fedorov Thanks for your help, I will try to update the plugin when v3.13 is released.

Artem Fedorov added a comment - 2018-11-02 10:23 https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/performance/3.13/performance-3.13.hpi