Actions
action #181574
opencoordination #177042: [saga][epic] Future ideas for higher quality os-autoinst+openQA product
coordination #181955: [epic] Improved package submission process
[spike][timeboxed:11h] Re-consider openQA-in-openQA OBS/Jenkins setup for staged packages size:S
Start date:
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
- The current setup involving jenkins together with openQA, OBS (and GHA) is not very robust and causes some kind of confusion every time something isn't working right. Maybe we can find an approach that is easier to maintain?
Suggestions¶
- Look into the current setup on http://jenkins.qa.suse.de/ using mostly scripts defined in https://github.com/os-autoinst/scripts/blob/master/trigger-openqa_in_openqa (and maybe others in that repo)
- Find a way to leave Jenkins out of the equation
- Maybe we can use Gitea features as OBS moves to git hosting?
- https://docs.gitea.com/usage/actions/quickstart
- YAML could be maintained in git, no need for another tool
- Consider Apache Airflow
- Rely on the openQA web UI
- Verify state of packages from within openQA
- OBS integration as a plugin?
Updated by livdywan about 1 month ago
- Copied from action #181526: osd-deployment fails during 'check openQA-in-openQA tests' size:S added
Updated by okurz about 1 month ago
- Subject changed from [spike][timeboxed] Re-consider openQA-in-openQA OBS/Jenkins setup for staged packages to [spike][timeboxed:11h] Re-consider openQA-in-openQA OBS/Jenkins setup for staged packages size:S
- Description updated (diff)
- Status changed from New to Workable
Actions