The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.
For a list of other such plugins, see the Pipeline Steps Reference page.
step([$class: 'MockLoadBuilder'])
: Mock Loadmock-artifact-*.txt
. There will be a JUnit test report with the file name mock-junit.xml
. Approximately 5% of the time, the build will "fail" its tests and thus no artifacts will be generated.
averageDuration : long
withMockLoad
: Mock load with separate sh commandGenerates load on the Jenkins build node and over the remoting channel. There will be a random number of build artifacts created matching the file name pattern mock-artifact-*.txt
. There will be a JUnit test report with the file name mock-junit.xml
. Approximately 5% of the time, the build will "fail" its tests and thus no artifacts will be generated.
Unlike the mockLoad
step, this step does not itself run the load command. Instead, it copies the program into the workspace and prepares a command for you to run yourself. Usage:
withMockLoad(averageDuration: 300) {
sh MOCK_LOAD_COMMAND
}
averageDuration : long
(optional)
Please submit your feedback about this page through this quick form.
Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?
See existing feedback here.