action #15132: [saga][epic] Better structure of test plans in main.pm [functional][y][timeboxed:6h] proof-of-concept of declarative test schedule definition, e.g. in YAML file(s)
Status: Resolved Start date: 28/11/2018 Priority: Low Due date: 26/02/2019 Assignee: riafarov % Done:
Category: Enhancement to existing tests
Target version: SUSE QA tests - Milestone 23
Show what can be done in a yaml file and have a base for discussion
Due date set to 12/02/2019
pre-fill last sprint in M22 with all tickets within milestone not yet assigned to sprints
Related to added action #16188: Easier way to clone jobs for test development
Status changed from In Progress to Workable
Priority changed from Normal to Low
PR has enough feedback but I don't fancy working on this ATM.
Don't you mind if I take over? I would spend a bit more time on that to provide solution which we could start using at least inside Y-team.
Assignee changed from okurz to riafarov
sure, go ahead. I would be happy to see you working based on my ideas or a different approach with own ideas just as same.
We have provided 2 working PoC, so let's gather feedback and decide how to proceed. I've also had a nice conversation with @kalikiana, and on of outcomes was that there might be new layer introduced, so we could introduce settings for combinations of mediums and machines, which would greatly simplify certain scheduling problems like choosing correct bootloader.
Status changed from Workable to Feedback
Due date changed from 12/02/2019 to 26/02/2019
We need more feedback to decide upon follow-up steps.
Related to added action #46667: Define version-able and human readable format for job scheduling-related tables
Copied to added action #47921: [functional][y] Apply new scheduling mechanism for any installation scenario in YaST job group which is also executed on o3
Target version changed from Milestone 22 to Milestone 23
Status changed from Feedback to Resolved
As I've created
#47921, I believe this is more than done. So I resolve it.
Also available in: