Gatling Enterprise 1.14
Learn about the main new features of Gatling Enterprise 1.14
Upgrading
Prior to upgrading, make sure to perform the required backups as described at the beginning of the Installation Guide.
Gatling Enterprise 1.14
Gatling Enterprise 1.14 introduce support for multiple versions of Gatling and performance fixes.
Gatling 3.6, 3.5, 3.4 and 3.3 generations support
Gatling Enterprise 1.14 is compatible with the 4 latest Gatling generations.
Only Gatling 3.6 will be actively maintained.
Multiple versions support is for convenience so that customers don’t have to upgrade all their tests when upgrading their Gatling Enterprise platform.
Customers are recommended to upgrade to Gatling 3.6 as soon as they can.
Key New Features
- faster crash when a simulation can’t be instantiated because of a user error (no more HTTP retries in this case)
- AWS subnets are no multivalued and retried randomly if deploying the pool fails because of insufficient capacity
- full Cassandra Java Driver configuration with Typesafe config (eg configuring TSL)
- the Gatling zip bundle now provides a script to generate uploadable artifacts (eg in an S3 bucket repository)
Key Bug Fixes
- several bug fixes related to group menu in Requests and Groups tabs
- updating a filesystem private key didn’t properly update the path
- TCP Connection states stats were missing when network was IPv6 while target was IPv4
Gatling 3.6.0
Gatling 3.6 becomes the production version, meaning that no further improvements and bug fixes will happen on Gatling 3.5.
Key New Features
- transparent support for Brotli compression
Key Bug Fixes
- several important bug fixes on HTTP/2 support. Upgrading is highly recommended if you use HTTP/2.
- several important bug fixes on async DNS resolution, on particular when used in combination with
shareConnections
Release Notes
1.14.3 (2021-07-06)
Gatling 3.6.1
Please check the full release note: https://github.com/gatling/gatling/milestone/97?closed=1
Gatling Enterprise
Fixes
- FL-693: Dashboard: Fix chart label with same color
- FL-695: Dashboard: Fix modal percentile overflow
- FL-696: API Tokens: Reload API Token table when an API Token is created
- FL-698: Dashboard: Fix highlight in tooltip
- FL-700: Simulation: Don’t truncate response payloads with non US-ASCII chars
- FL-706: Dashboard: Fix crash on pie and bar chart
- FL-708: Dashboard: Labelled component crash while updating the labels props
- FL-710: Dashboard: Trim errors messages so tooltips don’t grow too large
- FL-716: Dashboard: Fix DNS charts’ colors
- FL-719: Pipeline: Compute
startTimeout
’s default value based on configuredwaitHttpTries
- FL-753: Kubernetes/OpenShift: Retry on HTTP connect when failure is actually that the service behind the ingress/route is not ready yet
- MISC-89: CI: Make script display a specific error if the Gatling Enterprise url is malformed and ends with a
/
1.14.2 (2021-06-03)
Gatling Enterprise
Fixes
- FL-678: Compare runs button should be disabled when there is only 1 run
- FL-681: Fix Cassandra configuration backward compatibility
1.14.1 (2021-05-28)
Gatling Enterprise
Fixes
- FL-668: Crash on boot when using OIDC or LDAP
1.14.0 (2021-05-20)
Gatling 3.6.0
Gatling Enterprise 1.14.0 is compatible with Gatling 3.3, 3.4, 3.5 and 3.6.
Still, you’re recommended to upgrade to 3.6.0, older versions are no longer maintained.
This release ships lots of bug fixes, in particular on HTTP/2 support and async DNS resolution. Most noticeable new feature is Brotli support.
See full release note: https://github.com/gatling/gatling/milestone/98?closed=1
Gatling Enterprise
This release doesn’t perform any new database automatic migration if you’re upgrading from 1.13.1 or above.
Features
- FL-20: Pipeline: Immediately fail test when a simulation crashes on instantiation instead of retrying HTTP connection
- FL-396: Repository: Gatling zip bundle now ships a script to generate uploadable artifacts (eg in an S3 bucket repository)
- FL-474: Pools: Add nonProxyHosts option for HTTP proxy configuration
- FL-534: AWS: subnets are no multivalued and retried randomly if deploying the pool fails for insufficient capacity
- FL-589: Cassandra: Expose full Cassandra Java Driver configuration with Typesafe config (eg configuring TLS)
Fixes
- FL-19: Public API: Fix
abortAll
API permissions - FL-192: Reports: Tooltip should pass over navbar
- FL-287: AWS: Only display enabled regions
- FL-346: Simulation: Fix decoding failure when passing undefined rampUp and rampDown
- FL-449: Logout: CORS error on second logout
- FL-457: Logging: Clean up scheduler debug logs
- FL-476: Private Keys: Error when trying to delete a private key
- FL-486: Reports: Multiple highlights don’t clear when leaving graph
- FL-536: Azure: Filter out non suited instance types
- FL-541: Migrations: M00045_GitAndLocalSimulations doesn’t support old BitBucket SSH urls
- FL-552: Simulation: Double quotes are not escaped in System Props
- FL-558: Reports: Abscissa is broken on distribution charts
- FL-564: Pools: Select all shortcut (ctrl+a) on a multiple select input select add null to value
- FL-572: Reports: Last n minutes button doesn’t work if you’re zoomed in from the start of the run
- FL-573: Reports: Multiple highlights don’t clear when leaving graph
- FL-583: Reports: Tooltip vertical position is off when scrolling down
- FL-592: Reports: Changing Group in dropdown doesn’t update
- FL-595: Reports: Changing scenario unselect group* and selects the first real group instead
- FL-608: Reports: Navigator header is broken on small screen
- FL-609: Trends: Run comparison shouldn’t try to display runs that are currently injecting.
- FL-613: Reports: Can’t go to groups tab with group * if group none exists
- FL-616: Reports: JavaScript error when changing the OK/KO/All selection ona chart without data
- FL-619: Pipeline: Retry uploads on scp connection loss
- FL-627: Public API: Fix
abortAll
API - FL-630: Reports: Disable highlights refresh when test is running
- FL-631: Reports: Request menu gets emptied with only * when changing scenario with only group none
- FL-635: Boot: On First time configuration, Gatling Enterprise shows Cassandra error page instead of “Waiting for Gatling Enterprise to restart”
- FL-645: Reports: TCP Connection states stats are missing when network is IPv6 while target is IPv4
- FL-647: Private Keys: Invalid error message mentioning “Certificate” instead of “Private Key”
- FL-651: Private Keys: File system private keys path does not update