action #102548
open
coordination #72889: [qe-core][qem][epic] QAM move job groups, test suites, medium types to git, and then restructure QAM testing to be more easily comparable to product QA
[infrastructure] Ensure all jobgroups in osd and o3 display correct information on where they are being maintained
Added by szarate over 2 years ago.
Updated 3 months ago.
Description
As a result of #102134 it came out that also job groups don't have information on where they are being maintained
Ideally in both, o3 and osd we should be able to know where those are being mantained, if it's openQA webui (old way) or if a git repo is being used.
- Tracker changed from coordination to action
Oliver, I'm assiging it directly to you to so that you can better express the idea, feel free to assign back afterwards or we can refine this together over a coffee
For OSD, the job groups contain some header, e.g. https://openqa.suse.de/admin/job_templates/366?
I would think this is enough.
For O3 I haven't seen any example of job groups maintained outside the UI, but it would be nice to keep them in some github repo.. but yeah, this is a community decision.
- Subject changed from Ensure all jobgroups in osd and o3 display correct information on where they are being mantained to Ensure all jobgroups in osd and o3 display correct information on where they are being maintained
- Category set to Infrastructure
- Assignee deleted (
okurz)
Provided the necessary examples and references and fixed typo in subject. Unassigning again as suggested.
- Subject changed from Ensure all jobgroups in osd and o3 display correct information on where they are being maintained to [infrastructure] Ensure all jobgroups in osd and o3 display correct information on where they are being maintained
@maritawerner I doubt "[infrastructure]" is going to work as no squad will see this ticket anymore on their backlogs. IMHO a test-related squad needs to pick this task and ensure that it is followed up. Subtasks can be delegated to other squads.
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Also available in: Atom
PDF