Gatling Enterprise 1.12 Highlights
Gatling Enterprise 1.12 introduce scoped private keys, OpenId Connect and a permissions rewamp
Gatling Enterprise 1.12
Scoped Private Keys
Private Keys now target either
You are now required to fill this scope when creating new private keys.
Upgrading automatically updates existing private keys depending on their usage.
Revamped Roles with new Test Admin Role
We now have the following roles:
member): can view simulations and runs
tester(new): all of the above + can edit simulations and trigger runs
manager): all of the above + can edit repositories and associated private keys
admin): all of the above + can edit pools and associated private keys, users, global properties, API tokens and team settings (simulations quotas)
superAdmin is a special system admin. You should only use it to create system admins.
Team Simulation Quotas
Managing a global licenced pool of simulations amongst multiple project teams can be cumbersome.
System admins can now define
quotas on how many simulations a given team can use.
New OpenID Connect Integration
Gatling Enterprise can now integrate with your favorite OIDC provider such as Azure Active Directory or Okta.
New Pools Features
Pools can now be duplicated.
- Spot instances support
- Built-in certified images
- Preemptible instances support
- Image and Instance type support (using instance templates is now deprecated)
- Injector static IP support
- Service accounts support
The key new features are:
- official gradle support with the new
- new sequential scenarios
- TLSv1.3 is now enabled by default
This release also includes lots of performance and bug fixes. Please check the https://github.com/gatling/gatling/milestone/92?closed=1[full release note].
Upgrading Gatling version in your Projects
Gatling 3.4 is mostly source compatible with Gatling 3.3 but there are still a few minor breaking changes, please check the Gatling 3.4 Migration Guide.
The benefit is that you don’t have to upgrade all your projects at the same time you upgrade Gatling Enterprise when a new Gatling minor version breaks binary compatibility.
You can upgrade Gatling Enterprise first, your existing projects will keep on working, and upgrade them to newest Gatling progressively.
- supporting deploying Gatling 3.3 projects will be dropped at some point, possibly when we will release Gatling 3.5.0
- the Gatling 3.3 branch is frozen, meaning no bug fixes will be backported
Upgrading maven/gradle/sbt plugin version in your Projects
- for maven:
- for sbt:
- for gradle:
frontline-gradle-plugin, you are now required to use a specific layout and store your Gatling code under
src/gatling/scala. Please check the sample you can download from Gatling Enterprise’s web UI.
Upgrading your injectors JVM settings
We’ve updated the default JVM options to:
-server -Xmx1G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxInlineLevel=20 -XX:MaxTrivialSize=12 -XX:-UseBiasedLocking
and the default Java System properties are now empty.
Those new settings produced way better performance in our internal benchmarks.
If you’ve overridden the default global properties with your own parameters, you might probably want to revisit them.
Gatling Enterprise Binaries Distribution Platform Change
Download urls on the new server use the same pattern as the old one, eg:
Minimal Original Gatling Enterprise Version
If you are currently using a version of Gatling Enterprise older than 1.6.2, you can’t directly upgrade to Gatling Enterprise 1.12.0. You have to first upgrade to Gatling Enterprise 1.11.1.
Otherwise, if you are running Gatling Enterprise 1.6.2 or newer, you can directly upgrade.