Using JMeter 2.13, Maven and Linux in all servers. Not running any tests from gui or command line, Maven is used!
Have a test plan with a lot of parameters that are set and passed from Maven execution in Jenkins to the JMeter test plan. Using "-J" in Maven to set the input parameters.
Works fine in single JMeter environment.
If I start JMeter in slaves manually first, then start the Jenkins job the test plan in the specified remote servers are started properly. But I have observed that no parameters are transferred to the remote servers. So, I can't control the test plan execution.
The temporary workaround is to hardcode some parameters in the test plan.
But this is not acceptable solution!
I've looked around a lot. Have found these pages, JMeter distributed testing and command line parameters and this
But I'm running from Maven, not command line, so "-G" doesn't work!
Haven't done any RMI setup, but I don't think that's the problem.
Probably more related to how parameters should be transferred to remote servers.
With this setting in pom.xml,
According to the documentation:
Adding Additional Properties To propertiesGlobal
Global properties are properties that are sent to the remote machines. To set those properties you will need to specify each property in your pom.xml in the config element propertiesGlobal (The example below shows a property called threads and a property called testIterations being set).
<project> [...] <build> <plugins> <plugin> <groupId>com.lazerycode.jmeter</groupId> <artifactId>jmeter-maven-plugin</artifactId> <version>2.0.3</version> <executions> <execution> <id>jmeter-tests</id> <goals> <goal>jmeter</goal> </goals> </execution> </executions> <configuration> <propertiesGlobal> <threads>10</threads> <testIterations>5</testIterations> </propertiesGlobal> </configuration> </plugin> </plugins> </build> [...] </project>
So it looks like you need to move these properties to
<propertiesGlobal> from the