Let me begin with a short description of this article’s context…
What is Apache JMeter?
The Apache JMeter™ application is open source software, a 100% pure Java application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.
And what is Gradle?
Gradle is an open source build automation system that builds upon the concepts of Apache Ant and Apache Maven and introduces a Groovy-based domain-specific language (DSL) instead of the XML form used by Apache Maven of declaring the project configuration. Gradle uses a directed acyclic graph (“DAG”) to determine the order in which tasks can be run.
I both used Apache Maven and Gradle for my projects and I have to admit that Gradle is far more flexible, rebust and easy. Just check this comparison chart for further information. Anyway, this article is not about comparing Apache Maven and Gradle at all. So let’s begin…
Recently we decided to use Apache JMeter for some load and performance tests for our projects in Netaş (the company I work) and integrated it with our contionuous integration tool, Jenkins. by the way, I strongly recommend Apache JMeter for load/performance tests, it’s a factastic tool.
While integrating with Jenkins, we also needed a reliable Gradle plugin in order to run JMeter tests on Jenkins. So we found the Foragerr JMeter plugin which is actually a fork of Kulya JMeter plugin. It was fine and useful for a while but we began to have problems about setting Java min/max heap size since version 1.0.5
So, we have decided to create a new fork of this plugin and fix the issues. We also added support for XML optimization for XML outputs created by JMeter. And here it is…