Launch Entreprise Simulation

Gatling (Open-Source)
1

Gatling version: 3.13.5
Gatling flavor: [X ] java
Gatling build tool: [ X] maven

I am trying to launch remote simulation throw command line " mvn gatling:enterpriseStart" but i faces a issue.

My pom.xml configuration is :

			<configuration> 
				<simulationId>${GATLING_SIMULATION_ID}</simulationId>
				<packageId>${GATLING_PACKAGE_ID}</packageId>
				<apiToken>${GATLING_API_TOKEN}</apiToken>
				<!-- Empêcher la création automatique -->
				<failOnMissingSimulationId>true</failOnMissingSimulationId> 
			</configuration>

First - i am configuring env variables :

export GATLING_SIMULATION_ID=*****
export GATLING_PACKAGE_ID=****
export GATLING_API_TOKEN=***

Secondly, i am uploading package :
mvn gatling:enterpriseUpload

target package is well updated.

Thirdly, i try to launch simulation.
But new package & new simulation is created.

[INFO] — gatling-maven-plugin:4.16.3:enterpriseDeploy (enterpriseDeploy) @ my-gatling-tests —
[INFO] Package ‘my-gatling-tests’ (id=‘f58******’) deployed
[INFO] Package uploaded (id=‘f5*************’)
[INFO] Simulation ‘my.cloud.consulting.MySimulation’ (id=‘****’) deployed
[INFO]
[INFO] <<< gatling-maven-plugin:4.16.3:enterpriseStart (default-cli) < :enterpriseDeploy @ my-gatling-tests <<<
[INFO]
[INFO] — gatling-maven-plugin:4.16.3:enterpriseStart (default-cli) @ my-gatling-tests —
[INFO] Type the number corresponding to your choice and press enter
[INFO] [0]
[INFO] [1] my.cloud.consulting.MySimulation

Could you please help to identify, what is wrong on my configuration or launch parameters ?

2

Hello @samir.fettal,

The gatling:enterpriseUpload command is deprecated and not compatible with gatling:enterpriseStart.

The recommended approach for uploading your packages using the Maven plugin is to use gatling:enterpriseDeploy.

This command is designed to handle both package uploads and simulation registration, based on the descriptor file located at .gatling/package.conf.

For more details, refer to the Configuration as Code documentation.

In your case, a minimal .gatling/package.conf file might look like this:

gatling.enterprise.package {
  id = ${GATLING_PACKAGE_ID}
  simulations = [
    {
      id = ${GATLING_SIMULATION_ID}
      # FQCN = Fully Qualified Class Name
      # Example: example.BasicSimulation
      simulation = "<Fully Qualified Class Name>"
    }
  ]
}

By configuring your project this way, the gatling:enterpriseStart command will behave as expected.