Mark Collin

You could do this: https://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html

It's enough for the plugin to pick up these jars and then it will configure JMeter appropriately.

So is the issue here that global properties are not being sent out to the slaves? If so it sounds like a JMeter bug at first glance. We supply a...

That all looks to be working correctly, the global properties are being applied to the secondary as per: ```2020-08-14 21:07:19,994 INFO o.a.j.e.StandardJMeterEngine: Applying properties {runID=TEST_0010}``` Only global properties will be...

JMeter doesn't support that as far as I'm aware, it only passes global properties through to the secondary. It sounds like what you really want this: https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues/35

You can of course use the plugin to start up the secondary instances, then it will be configured in the same way as the master, the following IT POM may...

It is not possible to configure the plugin to arbitrarily run commands upon another machine to start up a JMeter server instance. You would need to run your project on...

We support setting a timestamp for individual test results: https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/wiki/Test-Results-File-Format#2 This is currently not passed through to report generation though

I'm making the assumption that this is a request to be able to modify the `resultFilename`, currently we generate this programatically. based on the test name.

The biggest problem implementing this is that we don't know the names of the .jmx files that are going to be used in advance, we use pattern matching to collect...