Actions
action #150992
closedcoordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #48641: [epic] Trigger openQA tests in pull requests of any product github pull request
[timeboxed][spike solution:20h] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/ size:M
Description
[timeboxed][spike solution:20h] openQA tests in pull requests to github.com/os-autoinst/os-autoinst-distri-opensuse/
https://progress.opensuse.org/issues/150992
Motivation¶
With #126950 we have good experience with automatically triggered openQA tests in pull requests to os-autoinst-distri-openQA. We should now explore triggering openQA tests to os-autoinst-distri-opensuse
Acceptance criteria¶
- AC1: New pull requests in github.com/os-autoinst/os-autoinst-distri-opensuse provide feedback to the pull request creator and reviewers from at least one test scenario executed for the pull request before merge
Suggestions¶
- Follow the documentation and consider the existing use case in https://github.com/os-autoinst/os-autoinst-distri-example/blob/main/.github/workflows/openqa.yml
- Read about what needed to be done for #126950 for openQA-in-openQA tests
- Extend the concept to os-autoinst-distri-opensuse
- Define one or multiple scenarios that is/are always run, for example "default" or "textmode", maybe configurable? For this task just hardcode
- Allow an easy way to specify a scenario to run e.g. a validation job or parameters for scheduling
- Consider to only run a very much stripped down test, e.g. just "boot_to_desktop" of an existing image that takes only 1m and convinces everybody
Out of scope¶
- Run workflows on GitLab or involving osd - likely this can be implemented separately
Actions