I’m trying to get gatling for javascript running in my mac, but I’m having issues downloading graalvm from my vpn. Hence, I’ve setup and configured graalvm manually to get this running.
I want to use the local version of graalvm for the gatling tests.
Does someone know how we can toggle off this auto download feature along with npm run -simulation command ?
I’m afraid we don’t currently have an option for that. There are possibilities for improving that, or for offering a standalone bundle with all dependencies already included, but no guarantees at the moment on if and when that could be done.
There is a workaround you can try in the short term: manually copy GraalVM to the folder where it would have been downloaded automatically (our CLI tool will detect that GraalVM is already present, and won’t download it again). It normally gets downloaded to the folder ~/.gatling/graalvm/<graalvm version>/. Note that:
You can override the ~/.gatling part with the --gatling-home command line option if you want.
At the moment, with the latest Gatling JS version, the GraalVM version would be 23.0.0.
And Gatling JS will also download dependencies from Maven central: if that doesn’t work in your environment, it could get more complicated to work around.
We have published a new version (3.13.104, based on Gatling 3.13.1) which includes:
Detection of NPM proxy configuration to download the Gatling runtime dependencies
Gatling runtime dependencies are now bundled in a single archive, which is downloaded from a GitHub releases page. If the automatic download fails, it’s now much easier to download and install it manually.
edit: To be clear, this also applies for your other question “JS SDK: “Resolving dependencies with Coursier” timeout in corporate network with proxy”. We now package GraalVM and all our Java libraries in a single download.