Running a JMeter test with Jenkins 2.138.3 using Performance Plugin (that uses Taurus)

1,656 views
Skip to first unread message

philippe...@gmail.com

unread,
Nov 16, 2018, 2:56:18 PM11/16/18
to codename-taurus
Hello,

My intention was to test with last Jenkins stable version v2.138.3, the Performance Plugin 3.13.

I followed documentation :
I have following versions:
python --version
Python 2.7.15
bzt -h
Usage: bzt [options] [configs] [-aliases]

BlazeMeter Taurus Tool v1.13.1, the configuration-driven test running engine
...


I get this error:
[jmeter_load_test] $ bzt --help
Performance test: You don't have global bzt installed on this Jenkins host. Installing it globally will speed up job. Run 'sudo pip install bzt' to install it.
Performance test: Checking virtualenv tool availability...
[jmeter_load_test] $ virtualenv --help
Performance test: No virtualenv found on this Jenkins host. Install it with 'sudo pip install virtualenv'.
Cannot run program "virtualenv" (in directory "/Users/Shared/Jenkins/Home/workspace/jmeter_load_test"): error=2, No such file or directoryBuild step 'Run Performance Test' changed build result to FAILURE
Finished: FAILURE

I then read this, and I guess I am facing what is described here:

Is this issue related to Jenkins default user as explained here ?

------------------------------------------------------------------------------------------------------

Therefore, as a second step change the Jenkins default user. Here’s how:

------------------------------------------------------------------------------------------------------

If so, I don't understand what exactly is the problem and why only this plugin requires this change ?

Also , it should be stated in docs what the correct answer is for example:

Thanks for clarification and sorry for noise if this has already been answered.

Thanks
Regards

grey....@gmail.com

unread,
Nov 16, 2018, 3:03:55 PM11/16/18
to codename-taurus
Hi, philippe.
I doubt here is the best place for such questions. Did you try to ask plugin developers before?

---
Taras

philippe...@gmail.com

unread,
Nov 16, 2018, 3:08:01 PM11/16/18
to codename-taurus
Hello,
Thanks for answer.

I thought it was the same team, as I saw Andrey Pokhilko was maintainer of the plugin.
Do you know where this question can be asked ?

Thanks

Regards

Andrey Pokhilko

unread,
Nov 17, 2018, 3:27:42 AM11/17/18
to codenam...@googlegroups.com

Hi,

It says that neither "bzt" nor "virtualenv" is available from inside Jenkins. This is exactly the direction to troubleshoot it. Maybe you have issues with PATH variable.

The simplest way to check is to add shell execution step to Jenkins doing things like:

echo $PATH

which bzt

bzt --help


If those commands don't work, review the PATH

--

Andrey

16.11.2018 22:56, philippe...@gmail.com пишет:
CAUTION: This email originated from outside of Broadcom. Do not click links or open attachments unless you recognize the sender and know the content is safe.

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/7664181a-e8ec-4a7a-92ff-ceae98ed8dcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

gbetan...@gmail.com

unread,
Dec 12, 2018, 1:47:20 PM12/12/18
to codename-taurus
Hi Andrey!!

I had the same problem as Philippe and did as you suggested a shell script with:

echo $PATH

which bzt

bzt --help

it ran fine, so, my question is, what I need to fix in jenkins so bzt can run directly using the performance plugin?

Andrey Pokhilko

unread,
Dec 13, 2018, 2:42:34 AM12/13/18
to codenam...@googlegroups.com

When you say "did as you suggested a shell script" - did you do it inside Jenkins job or just in your shell?

--

Andrey

12.12.2018 21:47, gbetan...@gmail.com пишет:

gbetan...@gmail.com

unread,
Dec 13, 2018, 6:51:52 AM12/13/18
to codename-taurus
inside of a Jenkins job, and it run fine.

but if I switch to the performance plugin, put the bzt test.yml command and run it then got the "You don't have global bzt installed on this Jenkins host"

artem....@blazemeter.com

unread,
Dec 14, 2018, 8:28:00 AM12/14/18
to codename-taurus
Hi all

I've a question which OS do you use? 

Artem

четверг, 13 декабря 2018 г., 14:51:52 UTC+3 пользователь gbetan...@gmail.com написал:

gbetan...@gmail.com

unread,
Dec 14, 2018, 8:44:31 AM12/14/18
to codename-taurus
macOS High Sierra
version: 10.13.6
Message has been deleted

artem....@blazemeter.com

unread,
Dec 14, 2018, 10:17:24 AM12/14/18
to codename-taurus
So,

It's known issue for mac OS that I don't know how to fix. My suggestion is use Linux 

Thanks,
Artem

пятница, 14 декабря 2018 г., 16:44:31 UTC+3 пользователь gbetan...@gmail.com написал:

mmal...@gmail.com

unread,
Apr 26, 2019, 12:37:44 AM4/26/19
to codename-taurus
Hi Philip,

Were you able to get this issue resolved (You don't have global bzt installed on this Jenkins host)? I am also having the same issue in a Windows Jenkins Slave PC where it throws the same error of Taurus not being recognized through the Performance Plugin. Interestingly when the YAML file is executed as a windows batch command through Jenkins it works fine. The problem is when the Taurus command is executed through the Performance Plugin in a Jenkins Slave which uses SSH to communicate with the Jenkins Slave. When the same Taurus command (bzt C:\Users\xxx\Documents\MyFirstYAML2.yml -report)  is executed on a Jenkins Slave which uses Java Web Start method it works perfectly.



C:\Jenkins_Workspace\workspace\Performance_Taurus_JMeter_Blazemeter_Demo>echo C:\Java\jdk1.8.0_181/bin;%PATH%;C:\Program Files\Taurus\bin;C:\Java\jdk1.8.0_181\bin;C:\Windows\System32 
C:\Java\jdk1.8.0_181/bin;%PATH%;C:\Program Files\Taurus\bin;C:\Java\jdk1.8.0_181\bin;C:\Windows\System32

C:\Jenkins_Workspace\workspace\Performance_Taurus_JMeter_Blazemeter_Demo>bzt --help 
Usage: bzt [options] [configs] [-aliases]

BlazeMeter Taurus Tool v1.13.4, the configuration-driven test running engine

Options:
  -h, --help            show this help message and exit
  -l LOG, --log=LOG     Log file location
  -o OPTION, --option=OPTION
                        Override option in config
  -q, --quiet           Only errors and warnings printed to console
  -v, --verbose         Prints all logging messages to console
  -n, --no-system-configs
                        Skip system and user config files

C:\Jenkins_Workspace\workspace\Performance_Taurus_JMeter_Blazemeter_Demo>exit 0 
Performance test: Checking global bzt installation...
[Performance_Taurus_JMeter_Blazemeter_Demo] $ bzt --help
Performance test: You don't have global bzt installed on this Jenkins host. Installing it globally will speed up job. Run 'sudo pip install bzt' to install it.
Performance test: Checking virtualenv tool availability...
[Performance_Taurus_JMeter_Blazemeter_Demo] $ virtualenv --help
Performance test: No virtualenv found on this Jenkins host. Install it with 'sudo pip install virtualenv'.
Cannot run program "virtualenv" (in directory "C:\Jenkins_Workspace\workspace\Performance_Taurus_JMeter_Blazemeter_Demo"): CreateProcess error=2, The system cannot find the file specifiedBuild step 'Run Performance Test' changed build result to FAILURE
Finished: FAILURE

soporteinf...@gmail.com

unread,
Jul 11, 2019, 4:36:31 AM7/11/19
to codename-taurus
Hi,

I found (in Linux) that the Performance Plugin do not use the same $PATH environment variable were is installed by default bzt. 

That's mean for example in Ubuntu bzt executable is installed in /usr/local/bin/bzt and work from the command line because your user have this path in the $PATH environment variable but like in your example above do not with the performance plugin because the plugin was trying to use /bin/bzt as path. 

I solve the problem creating a soft link from /bin/bzt to the path were is installed bzt.

It seems the same behavior in Windows to me so you need to find which $PATH is used by the performance plugin.

Regards

sashika wijesinghe

unread,
Oct 1, 2020, 2:00:49 PM10/1/20
to codename-taurus
I have configured the PATH in Jenkins, but I'm still getting the below error. Is this error still exists in MacOS?

Performance test: You don't have global bzt installed on this Jenkins host. Installing it globally will speed up job. Run 'sudo pip install bzt' to install it. Performance test: Checking virtualenv tool availability... [jenkins-performance] $ virtualenv --help Performance test: No virtualenv found on this Jenkins host. Install it with 'sudo pip install virtualenv'.

Reply all
Reply to author
Forward
0 new messages