How to run separately the zincCompiler, and the gatling execution steps in SBT?


I was wondering if the gatling-sbt-plugin, already supports a way to split the steps of the zincCompiler, and the actual gatling execution. Currently, the problem that I have, I have a jenkins job that every time I re-executed, it pull the changes from my git repo, and even though the source code hasn’t changed, SBT goes through the resolve dependencies step, and takes a long time to start executing the test.

The current idea, I have in mind, is to selectively execute the zincCompiler step, only if the code changed, otherwise, skip, and go to the execution.

I’m not sure if this is the right approach for this particular problem. Please any suggestions are welcome.

Carlos Torres

Hi Carlos