Hey Guys,
We are trying to encourage the people in our organisation to adopt the Gatling tool for load tests.
we are gathering info on the Build Tools that are supported by Gatling, and we found that the SBT, Maven and Gradle are being used.
we just want to highlight the facts on how to choose a build tool based on a certain situation, its features, pros, cons etc…
Based on your experience, what you guys think?
Thanks
Sujin Sam
Hi sujin sam,
My first guess would be to use the build tool known by the project team. Each build tool has its own environment and culture, better to use something that is well known.
If actual projects are not in the JVM world, I would go with SBT as it is the build tool used by Gatling team.
But we provide different build tools integration, it is up to you to choose what suits you best.
Regards,
I would beg to differ (same team, different opinions) 
• go with the tool your devs use if you’re a JVM shop
• maven is the most popular build tool on the JVM, you will be able to easily find people with maven skills and online resources
• gradle is popular too. Juste beware that the plugin for gatling was a third party but is about to become official but will go under some changes In the process.
• sbt is a complicated beast. I would recommend against going with it if you don’t have Scala devs in your org.
Thanks for the suggestions Stephane and Sebastien 
Our target audience are Testers who have less/no knowledge on the build tools
They will be going through learning process to adopt it
would one would be the right choice to start with and why it is?
Our target audience are Testers who have less/no knowledge on the build tools
“less”, perhaps some of them knows one of the beasts ^^
would one would be the right choice to start with and why it is?
More or less a religious debate here.
I stay on my position with SBT if you are sure that this “test” project will only use Gatling. But Stéphane is right, as the project grows, you will have to integrate with other build tools or other package systems, maven might be the right choice due to its history and (very) large community with tons of documentation available.
Thanks Sebastien 