Code changed in jenkins
User: Raphael Pionke
Path:
pom.xml
src/main/java/hudson/plugins/performance/AbstractParser.java
src/main/java/hudson/plugins/performance/PerformanceBuildAction.java
src/main/java/hudson/plugins/performance/PerformanceProjectAction.java
src/main/java/hudson/plugins/performance/PerformancePublisher.java
src/main/java/hudson/plugins/performance/PerformanceReport.java
src/main/java/hudson/plugins/performance/PerformanceReportMap.java
src/main/java/hudson/plugins/performance/PerformanceReportParser.java
src/main/java/hudson/plugins/performance/PerformanceReportParserDescriptor.java
src/main/java/hudson/plugins/performance/TestSuiteReportDetail.java
src/main/java/hudson/plugins/performance/TrendReportGraphs.java
src/main/java/hudson/plugins/performance/UriReport.java
src/main/java/hudson/plugins/performance/constraints/AbsoluteConstraint.java
src/main/java/hudson/plugins/performance/constraints/AbstractConstraint.java
src/main/java/hudson/plugins/performance/constraints/ConstraintChecker.java
src/main/java/hudson/plugins/performance/constraints/ConstraintDescriptor.java
src/main/java/hudson/plugins/performance/constraints/ConstraintFactory.java
src/main/java/hudson/plugins/performance/constraints/ConstraintReport.java
src/main/java/hudson/plugins/performance/constraints/RelativeConstraint.java
http://jenkins-ci.org/commit/performance-plugin/520a9a0ac3ab50abb78fbcdf10c89a500814caea
Log:
JENKINS-32650 make Performance Plugin Pipeline compatible (#73)

• replace Hudson.getInstance()

• make Performance Plugin Pipeline compatible

• add Symbol

• replace AbstractBuild occurrences

The issue seems to be done an merged into master. Will there be a new release soon?

I updated to Performance Plugin version 1.15 that added a new pipeline step performanceReport and the following problems occured (see also Github #73):

1. Missing PerformanceTrend in Job-View
   
2. Duplicated Performance Report in Build-View (see attachment)
   
3. Snippet generator cannot handle double values of relative thresholds

   performanceReport compareBuildPrevious: false, configType: 'MRT', errorFailedThreshold: 0, errorUnstableResponseTimeThreshold: '', errorUnstableThreshold: 0, failBuildIfNoResultFile: false, modeOfThreshold: false, modePerformancePerTestCase: true, modeThroughput: false, nthBuildNumber: 0, parsers: [], relativeFailedThresholdNegative: <object of type java.lang.Double>, relativeFailedThresholdPositive: <object of type java.lang.Double>, relativeUnstableThresholdNegative: <object of type java.lang.Double>, relativeUnstableThresholdPositive: <object of type java.lang.Double>
   

   I had to replace <object of type java.lang.Double> manually by the correct double values.

I need the PerformanceTrend in urgent. Do you have a plan to fix it as soon as possible? Thanks!

I'm maintaining this plugin by building releases mostly. So I'd love somebody to bring the pull request with bugfix. I myself not familiar with codebase good enough to fix it for now.

I created a bug ticket JENKINS-40508 and linked it to this one.

Hi, I generated the code for performance report using the snippet generator and manually replaced <object of type java.lang.Double> with double values. I got the below error when I use it in my pipeline : (I'm using plugin version 2.0)

java.lang.NullPointerException
at hudson.plugins.performance.PerformancePublisher.perform(PerformancePublisher.java:333)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:78)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:65)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49)
at hudson.security.ACL.impersonate(ACL.java:260)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Please can you advise me on this issue.

Thanks.

The Double issue is the well-known JENKINS-31967.

Code changed in jenkins
User: Jesse Glick
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/pipeline-plugin/c84a9af380854dbafd66e265b63cd05969ad7c47
Log:
Merge pull request #439 from alexbrjo/alexbrjo-compat-update

JENKINS-32263 JENKINS-32650 JENKINS-33841 JENKINS-33310 JENKINS-26591 JENKINS-30522 Updated support status for several plugins

Compare: https://github.com/jenkinsci/pipeline-plugin/compare/23d473486c8e...c84a9af38085

Code changed in jenkins
User: Oleg Nenashev
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/pipeline-plugin/d2fd0f3c633d758dccf95d70d52452a80e6cdd89
Log:
Merge pull request #444 from artem-fedorov/upd-blazemeter-and-performance-plugins

JENKINS-32650 update Performance plugin and BlazeMeter plugin compatibility

Compare: https://github.com/jenkinsci/pipeline-plugin/compare/9c5f16187aba...d2fd0f3c633d