action #122953

Updated by szarate 8 months ago

Too often, we need to either trigger multiple jobs to know if an intermittent test failure is gone or to try and catch a sporadic product bug or an issue somewhere in the infrastructure, so the story would go like this: 

 * As a developer, I would like the openQA client to trigger a list of jobs N times so I can catch a flaky testcase or reproduce a sporadic issue that doesn't affect other builds or JobGroups. 

 I'm looking for an extension of the [openQA Client code](; knowing how to extend the openQA Client will allow us to do even more in the future to support other squads. 

 #### Acceptance Criteria 

 1. Solution is documented in in a Section dedicated to statistical investigation 
 1. Solution is packaged and distributed with openQA-client 
 1. Job count is added to the name of the test 
 1. Allow for a PR (CASEDIR) also to be triggered 

 #### Notes 

 1. See and [Oliver's]( comment 
 1. TL;DR or already achieve but built-in into openqa-cli? 
 1. Initially we want a sensible amount of jobs, so we don't end up DoS'ing ourselves, so things like 1M jobs or even 1K, should be taken into consideration on how to approach that. 

 `openqa-statistics-whatever $JOB $TIMES $JOB_SETTINGS` 
 `openqa-clone-job ... --job-count 15 ...`