Project

General

Profile

Actions

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.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
2021-11-17
Due date:
% Done:

0%

Estimated time:
Difficulty:

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.

Actions #1

Updated by szarate over 2 years ago

  • 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

Actions #2

Updated by jlausuch over 2 years ago

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.

Actions #3

Updated by okurz over 2 years ago

Good examples are https://openqa.opensuse.org/group_overview/1 as well as https://openqa.suse.de/group_overview/110 . https://openqa.opensuse.org/group_overview/1 provides good information, how the product is tested, reviewed, points of contacts. https://openqa.suse.de/group_overview/110 is also mentioning the review process and contact information though that is highly outdated and should be updated. I suggest that every job group has at least a contact group or person to talk to, at best also some information about how the tests are triggered, reviewed, maintained.

Actions #4

Updated by okurz over 2 years ago

  • 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.

Actions #5

Updated by maritawerner over 2 years ago

  • 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
Actions #6

Updated by okurz over 2 years ago

@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.

Actions #7

Updated by slo-gin over 1 year ago

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.

Actions #8

Updated by slo-gin 3 months ago

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.

Actions

Also available in: Atom PDF