Plot and PerformanceReport plugin utilization with Jenkins 2.xx and Pipeline Scripts

[ribeiro...@gmail.com]

Hi everyone,

We're not being able to use either the Plot or PerformanceReport plugins with Jenkins 2.xx and the Pipeline Scripts.

Looking at the compatibility of plugins with the new jenkins pipeline, we are running short of options to show taurus/jmeter/blazemeter test results.

https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md

Do you guys recommend any alternative or approach?  (without reverting back to non-pipeline script Jenkins :) )

Thanks in advance,

Pedro Ribeiro

[Andrey Pokhilko]

Hi,

The only thing I can suggest here is to wait. We have plans to fix Performance Publisher plugin in the nearest future, but it takes time (we're working on JMeter 3.2 all plugins compatibility).

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/e3936af6-f415-4ff9-8744-4b18fed71d1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ribeiro...@gmail.com]

Thanks Andrey.

I will check with our Blazemeter account manager (I work for a company that has a Blazemeter corporate account) to see if we can help you guys beta test such plugin.

We really need it with urgency.

Thanks,

Pedro

[Andrey Pokhilko]

Hi,

There was Performance Plugin release 2.1 which added support for Taurus summary files. Worth looking at for you.

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

[Pedro Ribeiro]

Thanks Andrey, however it looks like it still isn't compatible with Jenkins Pipeline script code, so I can't use it myself yet :(

[Craig Rodrigues]

Pedro,

I was able to successfully run JMeter in a Jenkins Pipeline script,
and then use Pipeline Plugin 2.1 in the same Jenkins Pipeline script to process the results.

What problem did you have?

--
Craig

[Pedro Ribeiro]

Hi Craig,

Are you able to provide a Jenkins Pipeline syntax example that we can use as a base to try to get it to work?

We tried multiple combinations and we always ended up getting null pointer exceptions.

Looking at this page: https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md

its not one of the supported plugins, but if you got it to work, we would be thankful to get a working example!

Thanks!

Pedro

[Craig Rodrigues]

Pedro,

Yes, I was able to get it to work.  COMPATIBILITY.md should be used just as a guide,
since it is not accurately updated for every third party Jenkins plugin.

My pipeline looks something like this:

node {
    stage("Checkout scripts from git") {
         git  url:'someurl'
    }

    stage("Run JMeter command") {
        jmeter --version
        jmeter -n -J jmeter.save.saveservice.output_format=xml -t sample.jmx -l jmeter.jtl -j jmeter.log
        "
    '''
    }

    stage("Process JTL logs") {
        println "Test processing logs"
        /*
         * Use the Performance Plugin to process the .jtl log file.
         */
        performanceReport compareBuildPrevious: true,
                          configType: 'ART',
                          errorFailedThreshold: 100,
                          errorUnstableResponseTimeThreshold: '',
                          errorUnstableThreshold: 100,
                          failBuildIfNoResultFile: false,
                          modeOfThreshold: false,
                          modePerformancePerTestCase: true,
                          modeThroughput: true,
                          nthBuildNumber: 0,
                          parsers: [[$class: 'JMeterParser', glob: '**/*.jtl']],
                          relativeFailedThresholdNegative: 0,
                          relativeFailedThresholdPositive: 0,
                          relativeUnstableThresholdNegative: 0,
                          relativeUnstableThresholdPositive: 0
    }

    stage("Archive log files") {
        archiveArtifacts '**/*.jtl **/*.log'
    }

    stage("Cleanup") {
        // Wipe the workspace so we are building completely clean
        deleteDir()
    }
}

--
Craig

[Craig Rodrigues]

Woops, I made a typo in my last e-mail when I cut and paste my pipeline example.

You need something like:

node {
 stage("Checkout scripts from git") {
 git url:'someurl'
 }

 stage("Run JMeter command") {

 sh '''

[ribeiro...@gmail.com]

Thanks Craig.

I will soon give it a try and let you know how it goes.

I'm also keen to try the new TaurusParser released with version 2.1