Open JCL38-ORANGE opened 7 years ago
@JCL38-ORANGE thanks for the feedback, and great to hear you're finding the tool useful.
Regarding your first point , externalise some parameters located in the JMX file
, it is not currently possible. You'll need to re-generated the JMX plan with the modified parameters and re-run it. Although I can see the benefits of externalising some parameters; for example tune the number of threads without regenerating the JMX plan. I created issue #15 as a follow up.
By the way, do you have other uses cases where you can see the benefits of externalising these parameters ?
For the second point, I see the benefit of pulling the JMX plan from an external resource; an S3 bucket for example. These JMX plans can get very large quickly (makes it not convenient to pass it as a property in the deployment manifest), plus it can be much easier to automate that way. I also created issue #16 as a followup for this topic.
Hello,
We are using the jmeter-bosh-release at Orange. Thank you for the great job. I have generated a JMX test plan bu using JMeter instead of wizard usage. I would you like to externalize some parameters located in the JMX file : ThreadGroup.num_threads
ThreadGroup.ramp_time LoopController.loops HTTPSampler.domain How is it possible to achieve that ? Otherwise, do you plan an enhancement in order to store the jmx file on a s3 bucket storage ? Thanks and regards, JC.