Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: performance-plugin
-
Labels:None
-
Similar Issues:
Description
Jenkins ver:2.133
Performance Plugin:3.11
Compare reports with build number not working.
I run build #56 and I waited compare with build #53, check the log in jenkins console, it looks like correct to compare with #53. However when look performance report, it compares with the previous version #55.
I would like to confirm whether the number of changes shown in the report is related to the COMPARED_NUMBER in jenkins configuration. And why the performance report is not consistent with jenkins log.
Attachments
Activity
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?
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
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.
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
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.
OK
Will try to fix it on this week
Thank you very much for your help, looking forward to your good news.
Hi Artem Fedorov,
Is there any update for this issue?
Hi Liu Wang
I working on this issue now. I hope that I'll finished it today/tomorrow
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
fixed in 3.13
Thanks for your help, I will try to update the plugin when v3.13 is released.
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