Generates 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
}