When it comes to commercial use of this solution for true CI integration of perf testing into the build, we need to get our jmeter setup running on the main Jenkins server. The easiest (best) way to do this is to setup our cloud Jenkins as a slave to the main Jenkins. This has several advantages, not least of which is a transfer of perf testing resources to a dedicated cloud Jenkins, rather than running it on the main corporate server.
When setting up the Jenkins user for use by a master/slave it is important to get all the permissions correct for ssh. I found at first I could ssh with the Jenkins master/salve setup for the ‘ubuntu’ user but not the ‘jenkins’ user. But you need to use the ‘jenkins’ user in order to have all the correct permissions for the perf test.
(As an aside, after running with ‘ubuntu’ for testing purposes, I had to go over and delete a whole load of jars etc. that were now owned by ‘ubuntu’ on the jmeter controller)
Permissions for the various directories should thus be set to look like the equivalent ‘ubuntu’ user ones.
‘jenkins’ user home directory – location set by the Jenkins install I think: