Update the package to be run in GKE
start_test.sh command is called differently. See its help file and README.
Removed the original jmeter pdf reporter (takes ~40s to generate a single report and the report content lacks the details offered by the JMeter HTML one)
Added jtl log for each test and JMeter HTML report. They are pulled from the master pod packaged into a zip file.
The work paths on JMeter master and slaves are set correctly. Now the entire contents of a test plan directory (e.g. the demo path containing jmx, properties, csv, groovy, sql...) will be push to slave pods to be run. All paths in the jmx/properties can refer to the parent test plan folder.
Update the package to be run in GKE start_test.sh command is called differently. See its help file and README. Removed the original jmeter pdf reporter (takes ~40s to generate a single report and the report content lacks the details offered by the JMeter HTML one) Added jtl log for each test and JMeter HTML report. They are pulled from the master pod packaged into a zip file. The work paths on JMeter master and slaves are set correctly. Now the entire contents of a test plan directory (e.g. the demo path containing jmx, properties, csv, groovy, sql...) will be push to slave pods to be run. All paths in the jmx/properties can refer to the parent test plan folder.