action #106847
closedcoordination #104829: [Epic] Improve schedules for test suite in YaST group
Migrate a few more YAML schedules using PoC for enhanced scheduler
0%
Description
After working in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14241
we should try out to migrate a few more YAML schedule to evaluate this solution.
We should evaluate several things when doing it:
- How this approach would grow? 2-4 test suites should give us some idea.
- How clear are those default files to be used? Do you know which one to use right away?
- Is there any other way to set the defaults? It was considered not to have them in the schedule file because that would create too many schedule files, imaging that we split booloader and we have a different bootloader per type of machine.
Acceptance criteria¶
AC1: select 2-4 test suites and migrate them using new approach.
AC2: Provide feedback to the team about the point to evaluate.
Suggestions¶
- If the PR with with the PoC is still not merged, please, just cherrypick the commit(s).
- Check with @jrivera if any doubts about how to use this solution (as there is not documentation/unit tests/ci yet).
- Consider to recommend to file another ticket for similar activity so other team members can also have the experience to try out by themselves.
Updated by JERiveraMoya over 2 years ago
- Subject changed from Create YAML schedules using PoC for enhanced scheduler to Migrate a few more YAML schedules using PoC for enhanced scheduler
- Priority changed from Normal to High
- Target version set to Current
Updated by JERiveraMoya over 2 years ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
Updated by rainerkoenig over 2 years ago
- Status changed from Workable to In Progress
- Assignee set to rainerkoenig
Updated by rainerkoenig over 2 years ago
- Status changed from In Progress to Feedback
Migrated XFS test and USBinstall. The later one was tricky because it needed to split
up because of conditional schedule. The condition was resolved by creating a default-full.yaml
to apply for the Full medium FLAVOR.
VRs were started by providing the environment for YAML_SCHEDULE and YAML_SCHEDULE_DEFAULT manually.
Updated by JERiveraMoya over 2 years ago
- Status changed from Feedback to In Progress
Updated by rainerkoenig over 2 years ago
- Status changed from In Progress to Feedback
Updated by rainerkoenig over 2 years ago
Rebased my branch and corrected the file conflicts that were caused because meanwhile the "access-beta-distribution" was bulk-removed from all the YAML files, even those which were deleted by my branch.
PR#14849 should be ready to be merged now.
Updated by JERiveraMoya over 2 years ago
- Status changed from Feedback to Resolved