Project

General

Profile

Actions
Copy link

coordination #91914

closed

QA - coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

[epic] Make reviewing openQA results per squad easier

Added by okurz over 3 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
Ready
Start date:
2021-05-25
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

As a squad team member, I want to be able to more easily review Maintenance and Tumbleweed job group related test failures that are relevant to my squad.

Acceptance criteria

  • AC1: Squad members have access to a convenient review workflow of relevant openQA test failures

Suggestions

  • DONE Send out Rocket.Chat notifications via GitLab CI -> #91605
  • DONE Use custom hook scripts
  • DONE Have some page where you can choose the squad and then see its related tests for each SLE version -> #101187

Subtasks 3 (0 open — 3 closed)

action #91605: notifications about failed and unreviewed jobs - but using Slack (was: Rocket.Chat) size:MResolvedtinita

Actions
action #93065: "parallel_failed" jobs show up on /tests/overview?todo=1 but these do not need a labelResolvedokurz2021-05-25

Actions
action #110629: openqa-label-known-issues: Fallback notification address in openqa-label-known-issues if no email address could be parsed from group_overviewResolvedtinita2022-05-04

Actions

Related issues 5 (2 open — 3 closed)

Related to QA - action #52655: [epic] Move openqa-review from cron-jobs on lord.arch to a more sustainable long-term solutionResolvedokurz2021-04-19

Actions
Related to QA - action #93710: Reference individual openqa-review reports in gitlab CI artifacts, e.g. using gitlab pagesResolvedlivdywan

Actions
Related to openQA Project - coordination #166655: [epic] openqa-label-known-issuesNew2020-02-142024-11-27

Actions
Copied from openQA Project - coordination #91467: [epic] Surface openQA failures per squad in a single placeResolvedokurz2021-04-23

Actions
Copied to openQA Project - coordination #99306: [epic] Future improvements: Make reviewing openQA results per squad easierNew2016-02-09

Actions
Actions
Copy link
 #1

Updated by okurz over 3 years ago

  • Copied from coordination #91467: [epic] Surface openQA failures per squad in a single place added
Actions
Copy link
 #2

Updated by okurz over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by MDoucha over 3 years ago

  • Related to action #92533: Module-centric test result overview added
Actions
Copy link
 #4

Updated by okurz over 3 years ago

  • Description updated (diff)
  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from future to Ready
Actions
Copy link
 #5

Updated by okurz over 3 years ago

  • Related to action #52655: [epic] Move openqa-review from cron-jobs on lord.arch to a more sustainable long-term solution added
Actions
Copy link
 #6

Updated by okurz over 3 years ago

  • Related to action #93710: Reference individual openqa-review reports in gitlab CI artifacts, e.g. using gitlab pages added
Actions
Copy link
 #7

Updated by okurz about 3 years ago

  • Copied to coordination #99306: [epic] Future improvements: Make reviewing openQA results per squad easier added
Actions
Copy link
 #8

Updated by okurz over 2 years ago

  • Description updated (diff)
Actions
Copy link
 #9

Updated by okurz about 2 years ago

  • Status changed from Blocked to Resolved

All resolved

Actions
Copy link
 #10

Updated by okurz 2 months ago

Actions
Copy link

Also available in: Atom PDF