Run your Gatling Enterprise simulations from your TeamCity CI.
Purpose of this plugin
This plugin allows you to start a Gatling Enterprise simulation directly from your TeamCity platform. This plugin links a TeamCity plan with one and only one Gatling Enterprise simulation.
This plugin doesn’t create a new Gatling Enterprise simulation, you have to create it manually before.
To download the plugin, you need to get the zip file located at:
You need to be connected as an administrator of your TeamCity application to install it. Go Administration, Plugins List, Upload plugin zip, and choose the downloaded zip file.
Once the plugin is uploaded, you need to enable it.
The plugin needs some global configuration. Go Administration, then Gatling Enterprise.
The Address is the address of your Gatling Enterprise server, for example:
The Gatling Enterprise API Token is needed to authenticate to Gatling Enterprise. The API token needs the All role.
Add a new build step called Gatling Enterprise Launcher. Choose in the Simulation list the simulation you want to monitor. You need to configure the global properties of the plugin, and create at least a simulation on your Gatling Enterprise to do this step.
This step regularly prints a summary of the run’s current status to the build logs. By default, the summary is printed every 5 seconds the first 12 times (i.e. for the first 60 seconds), and then every 60 seconds. You can configure this behavior (or disable it completely) in the step configuration.
You can display the results of the Gatling Enterprise assertions as a JUnit Test.
Add a new build feature called XML report processing. Choose Ant JUnit as report type, and enter in the Monitoring rules input the following line:
A new Gatling Enterprise simulation will be started every time the job is run. Check the Console Log to check the advancement of the simulation. If the simulation ran successfully, it will look like the following:
If the Gatling Enterprise deployment fails (ie because of a shortage of available hosts), the plugin will retry 3 times to redeploy the simulation.
When the job run is finished, you will be able to see on the Gatling Enterprise Results tab, the summary of the Gatling Enterprise simulation.