Run on GKE and supporting all external files shipped with jmx #37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.