coordination #130850
Updated by okurz 11 months ago
## Motivation
Now we have a CI integration of openQA and pull requests on github can trigger openQA jobs and feed back the result. A challenge for big test matrices is to select which openQA jobs to execute. openqa-clone-custom-git-refspec for years can parse github description (and comments?) for openQA jobs to clone. That can now be integrated together to … be awesome
A comment like this or another format can be used in PR descriptions or commits to clone a job:
@openqa: Clone my/test/job/url
## Acceptance criteria
* **AC1:** openQA CI integration in any existing test distribution github project automatically runs openQA tests based on links to existing openQA jobs in the github description
* **AC2:** openQA documentation explains how the CI integration in *new* test distribution github projects can be setup to run as in AC1
* **AC3:** Same as AC1 but for any github comment
* **AC4:** One is able to customize test scheduling with additional test parameters, e.g. `@openqa http://my/openqa/t1 FOO=bar` or `@openqa BAR=eggs`
## Suggestions
* Read what was done originally in #63712 and the according pull request to openQA https://github.com/os-autoinst/openQA/pull/2618
* Try out openqa-clone-custom-git-ref with special comments
* Document this feature somewhere
* Additional test parameters specified are applied same as users are used to with openqa-clone-job - we don't expect to use the script but e.g. CloneJob.pm or refactor code as needed
* Split individual ACs into separate tickets if implementation gets too time consuming
* If you come up with something that works in a github workflow but becomes too big consider creating a github action repository or create an additional feature in our existing scripting