Currently we run a short performance test after each release, to establish a baseline of sorts.
It gets triggered by Jenkins job and resulting report is stored in Jenkins as well.
According to multiple sources it’s not a good practice to treat Jenkins job history as persistent storage (no backups etc).
My question: is there an example which extends the https://gatling.io/docs/current/realtime_monitoring beyond tracking
the simulation mid-flight?
For example to compare the results of running same scenario vs different builds of our software - currently we do it manually by opening 2 Gatling reports side-by-side.
Thanks in advance.