<p><a href="https://gatling.io/docs/2.3/extensions/jenkins_plugin/" rel="nofollow noreferrer">https://gatling.io/docs/2.3/extensions/jenkins_plugin/</a></p>

<p><a href="https://wiki.jenkins.io/display/JENKINS/Gatling+Plugin" rel="nofollow noreferrer">https://wiki.jenkins.io/display/JENKINS/Gatling+Plugin</a></p>

<blockquote>
  <p>Configuration</p>

<pre><code>Install Gatling Plugin (via Manage Jenkins -&gt; Manage Plugins)
Configure your project to execute Gatling simulations, for example using the Maven plugin (see Maven plugin documentation)
Configure your job :
    For a maven job: add "Track a Gatling load simulation" as a new post-build action. Beware that neither your Jenkin's path nor your
</code></pre>
  
  <p>job's name should contain any space.
          For a pipeline job: add a line to your pipeline script: gatlingArchive()</p>
  
  <p>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.</p>

<pre><code>Configure the Jenkins plugin with the following Test report XMLs: target/gatling/assertions-*.xml
Execute Gatling with the following option: -Dgatling.useOldJenkinsJUnitSupport=true, for example: mvn gatling:execute -Dgatling.useOldJenkinsJUnitSupport=true
</code></pre>
</blockquote>

CC BY-SA 3.0
2017-12-30T18:10:58.173Z
2017-12-30T18:10:58.173Z
030
<p><a href="http://gatling.io/" rel="nofollow noreferrer">Gatling</a> creates an HTML report:</p>

<pre><code>Reports generated in 0s.
Please open the following file: /path/to/target/gatling/recordedsimulation-1496161958749/index.html
[info] Simulation RecordedSimulation successful.
[info] Simulation(s) execution ended.
[success] Total time: 31 s, completed May 30, 2017 6:32:57 PM
</code></pre>

<p>What are best practices to read the output and check whether it is acceptable, i.e. if a certain value is larger and smaller than X? Should one create a custom script or does Gatling itself provide such a functionality?</p>

<continuous-integration><gatling>
What are best practices to implement Gatling in CI?
030
# What are best practices to implement Gatling in CI?

(Asked by: username_0 on 2017-05-30)

Gatling creates an HTML report:
Reports generated in 0s.
Please open the following file: /path/to/target/gatling/recordedsimulation-1496161958749/index.html
[info] Simulation RecordedSimulation successful.
[info] Simulation(s) execution ended.
[success] Total time: 31 s, completed May 30, 2017 6:32:57 PM

What are best practices to read the output and check whether it is acceptable, i.e. if a certain value is larger and smaller than X? Should one create a custom script or does Gatling itself provide such a functionality?

**Tags:** continuous-integration, gatling


---

## 1 answers

### Answer by username_0 on 2017-12-30. Score: 1 | Accepted answer

https://gatling.io/docs/2.3/extensions/jenkins_plugin/
https://wiki.jenkins.io/display/JENKINS/Gatling+Plugin

Configuration
Install Gatling Plugin (via Manage Jenkins -> Manage Plugins)
Configure your project to execute Gatling simulations, for example using the Maven plugin (see Maven plugin documentation)
Configure your job :
    For a maven job: add "Track a Gatling load simulation" as a new post-build action. Beware that neither your Jenkin's path nor your

job's name should contain any space.
          For a pipeline job: add a line to your pipeline script: gatlingArchive()
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.
Configure the Jenkins plugin with the following Test report XMLs: target/gatling/assertions-*.xml
Execute Gatling with the following option: -Dgatling.useOldJenkinsJUnitSupport=true, for example: mvn gatling:execute -Dgatling.useOldJenkinsJUnitSupport=true


---

