action #119617
closed
coordination #119836: [epic] Convert YAML schedules for YaST to be based on YAML default files
Unify SLES 15 SP3 and SLES 15 SP4 schedule files using yaml schedule based on default
Added by hjluo over 1 year ago.
Updated over 1 year ago.
Description
Motivation¶
Using schedule files that are based on default we should be able to keep the same test cases for both products, which means that we can have the same yaml schedule file but different default file per product, and in some cases per architecture/backend.
Acceptance criteria¶
AC1: Use the same test suites for SLE 15 SP3 and SLE 15 SP4
AC2: Create default files for each product/arch/backend
AC3: Deploy (move configuration) in openQA job group YaST Maintenance Updates
Suggestions¶
We would try to avoid the use of Flows, with default files should be sufficient to achieve this goal.
- Subject changed from Unifiy the sles15sp4 MU with default+flow after we endalbed it with libyui to Unifiy the sles15sp4 MU with default+flow after we enable it with libyui
- Project changed from openQA Tests to qe-yam
- Subject changed from Unifiy the sles15sp4 MU with default+flow after we enable it with libyui to Unifiy SLES 15 SP4 and SLES 15 SP5 yamls using yaml based on defaults
- Description updated (diff)
- Assignee set to tinawang123
- Target version set to Current
Assigning to Tina as follow up of #118993.
- Subject changed from Unifiy SLES 15 SP4 and SLES 15 SP5 yamls using yaml based on defaults to Unifiy SLES 15 SP4 and SLES 15 SP5 schedule files using yaml schedule based on default
- Status changed from New to Workable
- Subject changed from Unifiy SLES 15 SP4 and SLES 15 SP5 schedule files using yaml schedule based on default to Unify SLES 15 SP4 and SLES 15 SP5 schedule files using yaml schedule based on default
- Description updated (diff)
- Tags set to qe-yast-refinement
- Tags deleted (
qe-yast-refinement)
- Subject changed from Unify SLES 15 SP4 and SLES 15 SP5 schedule files using yaml schedule based on default to Unify SLES 15 SP3 and SLES 15 SP4 schedule files using yaml schedule based on default
- Description updated (diff)
- Status changed from Workable to In Progress
- Parent task set to #119836
- Status changed from In Progress to Resolved
Also available in: Atom
PDF