Actions
action #160206
closedcoordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #154780: [epic] openQA scenario definitions fully in git
Minimum working example for job templates YAML import/include/inherit in kernelqa-openqa-yaml size:S
Start date:
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
What we learned in #155218 and we want to define a good structure for cross-file re-use of scenario definitions. For this we want to take inspiration from the kernelqa-openqa-yaml approach.
Acceptance criteria¶
- AC1: Minimum working example for job templates YAML import/include/inherit exists in kernelqa-openqa-yaml
Suggestions¶
- Continue what tinita started in #155218 coming up with a unit test that would make up a minimum example, because manual examples get outdated -> Add tests for kernel schedule repo
Updated by okurz 6 months ago
- Copied from action #155218: [spike][timeboxed:30h] Use scenario definitions instead of job group templates for os-autoinst-distri-opensuse size:M added
Updated by openqa_review 6 months ago
- Due date set to 2024-05-25
Setting due date based on mean cycle time of SUSE QE Tools
Updated by tinita 6 months ago ยท Edited
https://gitlab.suse.de/kernel-qa/kernelqa-openqa-yaml/-/merge_requests/511 Add test for jobgroup_genconf.py
https://gitlab.suse.de/kernel-qa/kernelqa-openqa-yaml/-/merge_requests/512 Fix jobgroup_genconf example
Updated by tinita 5 months ago
I closed https://gitlab.suse.de/kernel-qa/kernelqa-openqa-yaml/-/merge_requests/512
For details see discussion
Actions