Global configuration to use existing jmeter

[Tong Sun]

Just as for the same .jmx file, I can open (test with) different version of jmeter, I don't want to specify which jmeter to use in yaml Configuration file. 

However, I'll get the following if my yaml doesn't specify which jmeter to use:

$ bzt quick_test.yml

17:33:55 INFO: Taurus CLI Tool v1.15.2

17:33:55 INFO: Starting with configs: ['quick_test.yml']

17:33:55 INFO: Configuring...

17:33:55 INFO: Preparing...

17:33:55 WARNING: Failed to check for updates

17:33:55 INFO: Will install JMeter into /Users/master/.bzt/jmeter-taurus/5.2.1

17:33:55 ERROR: Can't fetch https://jmeter.apache.org/download_jmeter.cgi

17:33:55 INFO: Downloading: https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.2.1.zip

17:33:55 ERROR: Error while downloading https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.2.1.zip: Unsuccessful download from https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.2.1.zip

100% [                                                          ] ETA:  --:--:--

17:33:55 ERROR: Internal Error: JMeter download failed: No more links to try

Is there anyway that I define which of my existing jmeter to use, say in some global yaml configuration file? thx

[DT]

When you install Taurus it generates .bzt-rc file in your home folder where default configuration lives.

You can put whatever overrides you want there, for example you can specify existing JMeter installation location as:

modules:
  jmeter:
    path: c:/somefolder/jmeter

Alternatively you can specify the path via -o command-line argument like:

bzt -o modules.jmeter.path=c:/somefolder/jmeter test.yaml

More information: Navigating your First Steps Using Taurus