Using JMeter with Jenkins

There are big advantages to use JMeter and Jenkins together. Continuous Integration and Test Automation become standards on the DevOps world, but the performance levels and system complexity are increasing day by day.

Luckily, with Jenkins we can integrate all JMeter tests in our pipeline process and better understand the details of our applications.

Some of the main benefits of using JMeter with Jenkins are:

  • Unattended test execution for each system

  • Logs of build failures and recovery steps

  • Secure and easy access to test reports of each build

  • Automate routine work

The Apache JMeter

Apache JMeter may be used to test performance of static sites, dynamic sites, and complete web applications. It can be used to simulate a heavy load on a server, group of servers, network or object to test its strength or to analyze overall performance under different load types.

Jenkins Installation

The Jenkins docs already have a page to help us with the Jenkins installation process.. This guide uses the .jar installation. Visit the Guided tour page if you want to use it too. Both will give you the same results.

Install the performance plugin

In order to integrate JMeter with Jenkins, we will work with the Performance Plugin.

Follow these steps to install it:

  1. From your Jenkins dashboard page go to: Manage Jenkins

  2. Go to Manage Plugins page;

  3. Click on the Available Tab and write 'performance' in the search field;

  4. Mark the installation checkbox and press the button: "Install without restart"

    performance plugin

  5. If everything goes well you will receive this confirmation screen:

    Install confirmation page

JMeter Installation

In order to Install JMeter follow these steps:

  1. Go to Apache JMeter download page

  2. Pick your download option based on your system: .zip for windows or .tgz to Linux (I’m on windows, so I get the .zip option)

  3. Extract the downloaded file in your preferred location. (e.g.: c:\jmeter)

  4. Now edit the file: <YOUR-JMETER-PATH>>\bin\; (e.g.: C:\jmeter\bin in my case)

  5. Add this command to last line of file:, save and close the file edit; command

  6. That command will help us to integrate the JMeter output into Jenkins.

  7. Now let’s create our JMeter test plan.

First JMeter Test Plan using a GUI

JMeter uses Test Plans to organize each test. Once configured Jenkins will call all test plans defined on a pipeline and then show the results inside the build reports. It means you need to set all Test plans on JMeter as a first step and then info to Jenkins which test it needs to call.

Follow these steps to create a Test Plan:

  1. Run the file: <YOUR-JMETER-PATH>>\bin\jmeter.bat to open the JMeter GUI; (e.g.: C:\jmeter\bin\jmeter.bat in my case)

    • To Linux user will be the

    • In a definitive installation you can set these commands to your path system or System variables

  2. From JMeter GUI go to File menu and then pick the New option;

  3. Fill a name to your test plan. (e.g.: Test Plan )

  4. Now on the left side, click with the right button on your test plan item, go through this path Add > Thread(users) > Thread Group, and select it.

    plan test screen

  5. Increase the Number of threads (users) to 5 at Thread Group and to 2 on the Loop Count;

  6. Now on the left side, click with the right button on your Thread Group item, go though: Add > Sampler > Http Requester and select Http Requester option;

    Thread Group

  7. At Http Request, Fill: The Name of test, the Server Name, and the Path Context; (e.g: Installing;; and /doc/book/installing/ )

    Http Request sample

  8. Repeat steps 6 and 7 more two times to different contexts/pages. (e.g.:

  9. Now our plan has 3 things to test.

  10. To add a visual report click with the right button on your Thread Group item, go though: Add > Listener > View results in table and select View results in table option;

    Save and run test plan

  11. Now let’s save our test plan. Click on "disk icon", give a name a save with a .jmx extension (e.g.:

  12. Now run the test and see the table results.

    test results

First JMeter Test Plan using terminal commands

Our test is working well in the graphical user interface, but in order to integrate it with Jenkins, it needs to run from the command line.

Follow these steps to test:

  1. From the terminal run the command:

    set JMX=c:\jmeter\bin\
    set JTL=c:\jmeter\reports\
    c:\jmeter\bin\jmeter -j %OUT%=xml -n -t %JMX% -l %JTL%
  2. If everything works well the report file will be create at indicated location by -l parameter:

    manual test results

Jenkins and JMeter running together

Now we have everything we need to execute JMeter from Jenkins. Follow these steps:

  1. From Jenkins dashboard go to New Item;

  2. Fill the item name (e.g.: JmeterTest), select freestyle project, then press OK;

  3. Go to Build Environment tab, click on Add build step, and select the option: Execute Windows batch command

  4. Now fill the field with same code we use to run JMeter at previous section:

    Jenkins JMeter build step

  5. Now go to Post-build Action tab, Click on Add post-build action then select Publish Performance test result report;

    This option comes from the performance plugin if you can see it now please check the previous section and make sure you have installed the plugin.

  6. Now Fill the source of our reports:

    Source of reports

  7. Now Save the project and then click on Build Now from jmeterTest page

  8. After the job finish, go to the Console output view to see the execution details.

    Execution Details

  9. Console output view you can access the Performance Report and you will see the JMeter report data.

    Report Execution Details

This page outlines how to use Apache JMeter with Jenkins. The instructions are intentionally simplified by running Apache JMeter on the Jenkins controller. Apache JMeter in a production Jenkins environment should be run on a Jenkins agent, not on the Jenkins controller. Learn more about Jenkins agents from the Using Jenkins agents page.

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?


See existing feedback here.