Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Do not use this plugin anymore. Use Performance plugin instead.

Due to the new ability of this plugin of handling junit reports as well as jmeter ones, JMeter-plugin has been renamed to Performance plugin


This plugin allows you to capture report from JMeter. Hudson will generate graphic charts with the trend report of performance and robustness.

Release 0.3.0 includes the feature of setting the final build status as good, unstable or failed, based on the reported jmeter error percentage.

Usage with Freestyle project

1. You can use ant and jmeter task for ant to launch tests on your web application
2. Your ant file may be similar to something like that:

<project default="all">
  <!-- Define an environment variable pointing to JMETER folder or change this -->
  <property environment="env"/>
  <property name="jmeter-home" location="${env.JMETER_DIR}"/>

  <!-- ant-jmeter.jar comes with jmeter, be sure this is the release you have -->
  <path id="ant.jmeter.classpath">
       location="${jmeter-home}/extras/ant-jmeter-1.0.9.jar" />

    classpathref="ant.jmeter.classpath" />

  <target name="clean">
    <delete dir="results"/>
    <delete file="jmeter.log"/>
    <mkdir dir="results/jtl"/>
    <mkdir dir="results/html"/>

  <target name="test" depends="clean">
      <testplans dir="test/jmeter" includes="*.jmx"/>

  <!-- This is not needed for the plugin, but it produces a nice html report
       which can be saved usin hudson's archive artifact feature -->
  <target name="report" depends="test">

  <target name="all" depends="test, report"/>


Hudson Configuration

In Hudson, configure the files or the repository containing the files to be parsed by JMeter plugin.

If you have are using version 0.3.0, you can configure the error percentage thresholds which would make the project unstable or failed.


To use the latest plugin release, you need to download, compile and install by hand. To do it, you need subversion, maven and java installed in your computer.

$ svn checkout https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/jmeter jmeter (username is 'guest' and password 'guest'
$ cd jmeter
$ mvn package
$ cp target/jmeter.hpi <path_to_hudson>/data/plugins



  • Added the possibility of using more than one jmeter-report file. In order to keep the last version behaviour, the trend graphs will appear on the front page of the Hudson job if only one report file is present, when several report files are present the graphs will appear only when you click on “Jmeter trend”.
  • Added a configuration page for the graphs, accessible form the “Jmeter trend” page. It permits to show only the n last builds or the builds within a range of dates, the configuration is saved in a cookie.
  • Added threshold parameters in order to report the build process as unstable or failed based on the error percentage.
  • Fixed some bugs related with the parsing of previous-builds not configured for jmeter tasks.
  • Improvement of the plugin's performance when generating the graphs.
  • Added support for non-http XML report files.

NOTE: There is an incompatibility with the previous version of the plugin, due to the way the JMeter result files are handled:

- The Maven JMeter plugin handles the test result in this way now:
  * A test myJmeterTest.jmx produces a result file myJmeterTest-yyMMdd.xml where the date is the execution date of the test.

- The last released version (0.2) of the Hudson JMeter plugin only handles one JMeter test:
  * When the build finishes the JMeter result file myJmeterTest-yyMMdd.xml is copied to the root of the build directory and renamed to "jmeter.xml".

- But version 0.3.0 introduces the possibility to handle several JMeter tests :
  * When the build finishes the JMeter result files myJmeterTest-yyMMdd.xml and myOtherJmeterTest-yyMMdd.xml are copied to the build/jmeter-reports directory and renamed to "myJmeterTest.xml" and "myOtherJmeterTest.xml"
  * The result file name is used to keep track of each test when building the trend graphs, we cannot use anymore the hardcoded file name "jmeter.xml"
  * Unless the unique JMeter test file is called jmeter.jmx, there is no way to make the 2 versions of the plugin compatible.

- To keep the current test results obtained with the 0.2 plugin one has to apply the following migration procedure :
  * Rename the result file jmeter.xml found at the build root to "nameOfTheJmeterTest.xml"
  * Move the result file "nameOfTheJmeterTest.xml" to the build/jmeter-reports directory
  * The procedure has to be performed for all the existing builds


handling jmeter log format v 2.0


first release


  1. Unknown User (elser)

    Thanks for the plugin, it's great. I think however, that min and max times are swapped. Also, as can be seen on the page linked below, average time is sometimes greater than max time, which is improper, i think.


  2. Unknown User (josh@chapterthree.com)

    Indeed. In addition to the note above, it appears that the min/max may be on different scales (I see graphs where both min and max are below the average), and the min/max appear to be the actual literal min/max rather than a 5th/95th percentile or the like.

    It would be really amazing to get some configuration options for a threshold for how min/max are computed.

  3. Unknown User (venus)

    Please make the plugin version 0.3 available in the downloads section.

  4. Unknown User (jakub.gemrot@gmail.com)


    Thanks for cool plugin, I've got a bugreport...

    hudson.plugins.jmeter.JMeterReport. assumes that samples are always inside tag <httpSample> but that is a wrong assumption, according to http://jakarta.apache.org/jmeter/usermanual/listeners.html it may be <sample> too. Quick fix to JMeterReport (SAX parsing) will fix that.

    I stumble upon that measuring response time of my web service - Web Service (SOAP) sampler logs into <sample> tags.


  5. Unknown User (manuel_carrasco)

    @Venugopal Shenoy: I've uploaded version 0.3 to the download page.

    @Jakub Gemrot: Version 0.3 includes the fix for this issue.

    Thanks for suggesting and reporting

    Manuel Carrasco Moñino