Package Configuration

Configure and upload your package to Gatling Enterprise.

Managing#

To access the Packages section, click on Packages in the navigation bar. You need the Test Admin role to access this page.

The Packages view contains all the packages you have configured with the given name, team, filename of the uploaded package if not empty and the date of the last upload.

The Gatling version of the package is displayed in a badge next to the filename.

Creation#

In order to add a package, click on the “Create” button above the packages table.

• Name: the name that will appear on the simulations general step.
• Team:
  • you can select Global so that all teams have access to the package;
  • or select Specific and choose a single team which will own the package.

Upload#

Option 1: Manual Upload#

In order to fill the package with your bundled simulation, click on the icon on the right side of the table.

You can then drag and drop your package to fill the form and click on the Upload button.

You can upload multiple packages concurrently. Uploads progress will be shown in the Packages table.

You can cancel an upload in progress by clicking on the cancel icon.

Option 2: API Upload#

You can also upload packages programmatically with our REST API.

You’ll need:

• an API token with at least the Packages permission
• the Package’s ID, which can be copied from the WebUI.

You can then upload your package, eg with curl:

curl -X PUT --upload-file <PACKAGE_LOCAL_PATH> \
  "https://<DOMAIN>/api/public/artifacts/<PACKAGE_ID>/content?filename=<PACKAGE_FILE_NAME>" \
  -H "Authorization:<API_TOKEN>"

Option 3: Plugin configuration#

Maven, SBT and Gradle plugin offer commands to upload the generated package if properly configured. Check the Maven, Gradle, SBT plugin extensions for more information.

Usage#

You can configure which package to use for a simulation in the simulation’s General step.

Edit this page on GitHub