Actions
coordination #127910
closedcoordination #127031: [saga][epic] openQA for SUSE customers
[epic] openQA in SLE modules
Start date:
2023-03-01
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
Tags:
Description
Motivation¶
SUSE customers build their own products based on SUSE products including SLE, OBS, openQA. For a consistent supported base openQA should be usable on SLE. Additional to #127028 there is the request to offer openQA and all dependencies in SLE modules so not relying on PackageHub or any external dependencies
Acceptance criteria¶
- AC1: openQA (webUI+worker) is fully usable on latest SLE without needing PackageHub or external repositories
- AC2: openQA is continuously built+tested+published on latest SLE
Suggestions¶
- Follow #127028
- Automatically submit to SLE with an approach equivalent to http://jenkins.qa.suse.de/job/submit-openQA-TW-to-oS_Fctry/
- The artifact archive with the package lists of all os-autoinst+openQA dependencies is available in the latest pipeline run within https://github.com/os-autoinst/scripts/actions/workflows/obs-list-dependencies.yml so we should aim to have all packages listed from there coming from SLE modules
Further details¶
- Internal reference: https://confluence.suse.com/pages/viewpage.action?pageId=1127973305 and subpages
- Our internal stakeholders for the story are hsehic+szarate
Updated by okurz over 1 year ago
- Copied from coordination #127028: [epic] openQA on SLE+packagehub added
Updated by okurz over 1 year ago
- Status changed from Blocked to New
- Assignee deleted (
okurz) - Target version changed from Ready to future
See subtask update
Updated by okurz over 1 year ago
- Related to action #127883: Cleanup OBS project devel:openQA:Leap:15.4 added
Updated by okurz 3 months ago
- Status changed from Blocked to Resolved
- Target version changed from future to Ready
As clarified in a meeting with mkittler, hrommel, jstehlik, hsehic, okurz 2024-09-24 (private minutes in #165683-36) we should use SLFO as a base instead of SLE for a potential SUSE offering hence for now no further follow-up is planned here. Further work is conducted as part of #129313
Actions