Jenkins plugin for Gatling
36
stars
98
commits
Java
primary language
Jun 16, 2025
updated
This plugin integrates Gatling, an Open Source stress tool, with Jenkins.
This plugin allows you to :
Changelog is now published on github releases
A XSS vulnerability was fixed in the version 1.3.0 of the plugin, be careful when using older version of the plugin.
If you're coming from 1.0.0, make sure "Enable simulation tracking"
checkbox is checked in your build configuration and if not, check it.
This is an issue with configuration changes between 1.0.0 and 1.0.1 and doesn't affect fresh 1.0.1 installations.
Optional configuration: You can publish Gatling results with the Jenkins JUnit plugin. Your Gatling simulation needs to have some assertions, as each Junit testcase is a different Gatling assertion.
Gatling Plugin will look for files under your Job Root Directory
(defaults to $JENKINS_HOME/yourjobname), so you may need to copy the
results file if you're doing a containerized job.
As soon as you've properly configured your job and launched a build, you'll see two changes on your project dashboard :

The Gatling entry in the left summary has two purposes, depending on which page you are.
If you are on the project dashboard, clicking on Gatling will get you to a more detailed performance trend, displaying for your last 30 builds :
This page will also provides links to download the html reports for all your builds, at the bottom of the page.
If you are on the summary of a specific build, clicking on Gatling will get you to a list of all available reports for this build.
If you want to report issues, please use main Gatling project.
Java
100.0%
Jenkins plugin for Gatling
36
stars
98
commits
Java
primary language
Jun 16, 2025
updated
This plugin integrates Gatling, an Open Source stress tool, with Jenkins.
This plugin allows you to :
Changelog is now published on github releases
A XSS vulnerability was fixed in the version 1.3.0 of the plugin, be careful when using older version of the plugin.
If you're coming from 1.0.0, make sure "Enable simulation tracking"
checkbox is checked in your build configuration and if not, check it.
This is an issue with configuration changes between 1.0.0 and 1.0.1 and doesn't affect fresh 1.0.1 installations.
Optional configuration: You can publish Gatling results with the Jenkins JUnit plugin. Your Gatling simulation needs to have some assertions, as each Junit testcase is a different Gatling assertion.
Gatling Plugin will look for files under your Job Root Directory
(defaults to $JENKINS_HOME/yourjobname), so you may need to copy the
results file if you're doing a containerized job.
As soon as you've properly configured your job and launched a build, you'll see two changes on your project dashboard :

The Gatling entry in the left summary has two purposes, depending on which page you are.
If you are on the project dashboard, clicking on Gatling will get you to a more detailed performance trend, displaying for your last 30 builds :
This page will also provides links to download the html reports for all your builds, at the bottom of the page.
If you are on the summary of a specific build, clicking on Gatling will get you to a list of all available reports for this build.
If you want to report issues, please use main Gatling project.
Java
100.0%