I solved this by basing my gatling simulation off
sbt-plugin example project, then in Jenkins I'm using Declarative Pipeline to execute 2 simulations at one stage, and at later stage execute the gatlingArchive step.
This is my edited pipeline script:
pipeline {
agent { label 'gatling' }
stages {
stage ('Checkout') {
steps {
git credentialsId: '*********-****-****-****************', url: 'https://user...@git.server.com/UserName/gatling-scripts.git'
}
}
}
stage ('Gatling') {
steps {
parallel (
"test on lab1" : { sh "sbt 'gatling:testOnly MyPackage.ivan_test_on_lab1'" },
"test on lab2" : { sh "sbt 'gatling:testOnly MyPackage.ivan_test_on_lab2'" }
)
}
}
stage ('ArchiveResults') {
steps {
gatlingArchive()
}
}
}
After this job runs, both reports are available for this run - moreover, they are both displayed on the graph for this job.