Checkout under Dynamic Folder in the latest version (Version 3.0.0)

[Sumanta Chakraborty]

In previous versions 2.8.6 ( I was using) the checkout was happening in target/jmeter in the latest version it is creating a dynamic folder and doing the checkout. 

Is there any parameter to checkout under target/jmeter because I have some custom tasks which depends on this folder structure.

[Ardesco]

Version 3.0.0 onwards will create a unique directory for each run.  

If you have a look in the config.json you will see the directory associated with the the profile of the last run of the configure phase.  You could parse this file to collect the directory location that was last used.

[sth...@gmail.com]

Why isn't there an option to control this?  I should be able to run mvn clean if I need a brand new build, otherwise keep what's there and skip the jmeter install/build process.

[Ardesco]

Every time you go through the configure process it will configure a new JMeter instance, this allows us to have multiple profiles with different tests/libraries configured in them that can be used at a later stage.

See this bug for more context on why these changes were made:

https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues/230

[Shaun Thompson]

Sure but for those that aren't using or need that functionality should be able to override it and not have to go through the recreate/build jmeter process - IMO

--
You received this message because you are subscribed to a topic in the Google Groups "Maven JMeter Plugin Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/maven-jmeter-plugin-users/FcEHv55Kt_M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to maven-jmeter-plugi...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/maven-jmeter-plugin-users/b18b7116-29d6-4ebc-8980-0cc4618b2dce%40googlegroups.com.

[Ardesco]

We are using maven phases, if you run the configure phase multiple times it will configure multiple JMeter instances.  If you run the configure phase once, it will only configure a single JMeter instance.  If you don't run the configure phase it will not configure an instance of JMeter.

The main difference is that because you can have multiple JMeter configurations, we don't stick them all in the same folders, because if we did they would overwrite each other.

There is also a single file that is always in the same place that directs you to the folders that have been created by 1 - n configuration profiles.

I'm not sure I understand the issue here, the results are all placed in a central location, and there is a way to find out the folder location of each configuration associated with a specific profile.

On Wednesday, 15 January 2020 18:01:01 UTC, Shaun Thompson wrote:

Sure but for those that aren't using or need that functionality should be able to override it and not have to go through the recreate/build jmeter process - IMO

On Wed, Jan 15, 2020 at 11:42 AM Ardesco  wrote:

Every time you go through the configure process it will configure a new JMeter instance, this allows us to have multiple profiles with different tests/libraries configured in them that can be used at a later stage.

See this bug for more context on why these changes were made:

https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues/230

On Wednesday, 15 January 2020 17:17:02 UTC,wrote:

Why isn't there an option to control this?  I should be able to run mvn clean if I need a brand new build, otherwise keep what's there and skip the jmeter install/build process.

On Friday, January 3, 2020 at 5:28:16 AM UTC-6, Sumanta Chakraborty wrote:

In previous versions 2.8.6 ( I was using) the checkout was happening in target/jmeter in the latest version it is creating a dynamic folder and doing the checkout. 

Is there any parameter to checkout under target/jmeter because I have some custom tasks which depends on this folder structure.

--
You received this message because you are subscribed to a topic in the Google Groups "Maven JMeter Plugin Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/maven-jmeter-plugin-users/FcEHv55Kt_M/unsubscribe.

To unsubscribe from this group and all its topics, send an email to maven-jmeter-plugin-users+unsub...@googlegroups.com.

[Shaun Thompson]

The issue is that I'd rather not waste that time and space configuring JMeter when it's not necessary for my use case.  This would be an easy option to add to the plugin to flag and detect.

Tying the configuration to a certain maven phase to run it only once is not intuitive and doesn't appear to work.

When running configure and then running jmeter in separate mvn cmds throws the following exception.

```

Caused by: java.lang.NullPointerException
    at com.lazerycode.jmeter.configuration.RemoteArgumentsArrayBuilder.buildRemoteArgumentsArray (RemoteArgumentsArrayBuilder.java:23)

```

To unsubscribe from this group and all its topics, send an email to maven-jmeter-plugi...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/maven-jmeter-plugin-users/b18b7116-29d6-4ebc-8980-0cc4618b2dce%40googlegroups.com.

--

You received this message because you are subscribed to a topic in the Google Groups "Maven JMeter Plugin Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/maven-jmeter-plugin-users/FcEHv55Kt_M/unsubscribe.

To unsubscribe from this group and all its topics, send an email to maven-jmeter-plugi...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/maven-jmeter-plugin-users/145a7d4b-e755-4a68-bd96-5a79957adc70%40googlegroups.com.

[Ardesco]

In previous versions of the plugin (1.x and 2.x) the process to download and configure JMeter occurred every time you ran a test because we were not using the maven phases correctly.  This means that if you ran 2 tests one after the other, your first test run would be cleaned out and overwritten when the second test run happened.

Configuration is tied to a specific maven phase because that's the way maven is supposed to work.

If you run compile and then jmeter in separate commands it should work fine, the compile command will generate the config.json and then when you run the jmeter tests it will find the config.json and use it.  

mvn clean compile
mvn jmeter:jmeter

If you are cleaning in between commands, however it won't work because the clean command will clean out your target directory (e.g. mvn clean compile, followed by mvn clean jmeter:jmeter

if you just want to run everything as one you should just use 

mvn verify

Doing this will generate a new JMeter instance in your target folder and then run tests using it so that you don't lose your old test run, so you can run this multiple times and end up with multiple isolated folders.

This has been thought about to give you maximum flexibility, whilst trying to ensure that old test runs (and old configured Jmeter instances) are not lost unless you specifically want to remove them (using the clean command)

To unsubscribe from this group and all its topics, send an email to maven-jmeter-plugin-users+unsub...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/maven-jmeter-plugin-users/b18b7116-29d6-4ebc-8980-0cc4618b2dce%40googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Maven JMeter Plugin Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/maven-jmeter-plugin-users/FcEHv55Kt_M/unsubscribe.

To unsubscribe from this group and all its topics, send an email to maven-jmeter-plugin-users+unsub...@googlegroups.com.

[TINGTING ZHOU]

hi team, I have a similar question in another discussion. How can I add files to target/<uniqueID>/jmeter/bin? How did you generate the uniqueID? thanks. 

[João Nunes]

I have a very similar view to Shaun Thompson, it annoys the crap out of me that I can't avoid having multiple folders with basically the same content each time I run the tests.
I get the whole "managing different versions/complex setups" but why won't you give us the option to override this? Seems pointless to waste time and resources duplicating a directory over and over, especially when you're debugging tests.

Glad I found this message/post, I was about to open an issue about this.
Please give us an option to specify the Jmeter location and avoid overriding it when using the same version. Managing different versions could be easily achieved by appending the jmeter version to the path and then just keeping my multiple jmeter-x.x.x directories in the target/ directory. On each run you only have to check if target jmeter version exists and override config files. This should be 1000x faster than constantly initializing a 54Mb folder.