action #119746
[spike][timeboxed:20h] Filter openQA todo-jobs on /tests belonging to one "review squad"
0%
Description
Motivation¶
Also see #118639. The idea is to be able to find openQA jobs that need review as they block approval of maintenance updates. To find jobs needing review we can already use the "todo" checkbox on /tests but we also need to filter out jobs in "development" or outside any job group as well as match on either the job group name, e.g. match "Core Maintenance" or match on not "Kernel Maintenance".
Suggestions¶
- Proof of concept spike solution to filter jobs on /tests based on job group and job name. To be most flexible regex should be supported including also negative matches to exclude job names or job groups
Related issues
History
#2
Updated by okurz 3 months ago
Updated by - Related to action #117655: Provide API to get job results for a particular incident, similar to what dashboard/qem-bot does size:M added
#6
Updated by mgrifalconi 2 months ago
Updated by Hello, we were thinking on something similar but on the dashboard.qam.suse.de since it feels the point of integration between openQA and SMELT. But any place is good, important is to fullfill the goal :)
As a reviewer (for my squad or openQA review task) I would like to see:
- all failures related to a squad
- ordered by how many release requests they are blocking (to help prioritize)
- for how many runs (or days) they have been failing
From that view, we can also start collecting long term metrics, maybe with a CI in gitlab and feed into Grafana
Ideas of metrics:
- failures/day
- days before a failure is fixed
- number of release requests blocked
- morning vs evening failures (how much manual work was done to improve situation)
What do you think? How can we contribute?
Updated by