Project

General

Profile

action #17252

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

coordination #91914: [epic] Make reviewing openQA results per squad easier

notifications to maintainer on failed modules

Added by okurz almost 5 years ago. Updated 4 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2016-02-09
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

user story

As a test module maintainer I want to get informed about failure occurences so that I do not need to poll myself

acceptance criteria

  • AC1: For every occurence of a failed module in a job with no bugref or label where a person is registered as maintainer, this persons receives a notification
  • AC2: No notification is sent unless the maintainer opts-in
  • AC3: No notification is sent if the job within which the module fails has a bugref or label already

suggestions

  • listen to AMQP notifications for failed or softfailed jobs
for every reported job
  if not (bugref or label)
    for every failed module
      query maintainer
      if opt-in
        send notification

further details

  • probably we should start with a standalone script which can be run in a loop or persistent daemon, later on make it a server available to multiple persons registering, each storing their information in a database OR within openQA
  • subscribe/unsubscribe by email with sending email
  • subscribe/unsubscribe by IRC with sending query message to bot

Related issues

Related to openQA Project - coordination #91467: [epic] Surface openQA failures per squad in a single placeResolved2021-04-23

Copied from openQA Project - action #16276: notifications about failed and unreviewed jobsResolved2016-02-09

History

#1 Updated by okurz almost 5 years ago

  • Copied from action #16276: notifications about failed and unreviewed jobs added

#2 Updated by okurz over 4 years ago

  • Assignee deleted (okurz)

not currently working on this

#3 Updated by coolo about 4 years ago

this doesn't really look like an openqa feature, more a feature on top of #16276 - taken that openQA has no concept of 'maintainer'

#4 Updated by okurz over 2 years ago

  • Category changed from 140 to Feature requests

#5 Updated by okurz over 1 year ago

  • Target version set to future

#6 Updated by okurz 8 months ago

  • Related to coordination #91467: [epic] Surface openQA failures per squad in a single place added

#7 Updated by okurz 6 months ago

I was playing around learning about "associative arrays" in bash, like a dictionary or hash, and came with https://github.com/okurz/os-autoinst-distri-opensuse/blob/feature/read_maintainer/tools/find-maintainer , a trivial script to read out maintainer of each test module in os-autoinst-distri-opensuse

#8 Updated by okurz 5 months ago

  • Parent task set to #91914

#9 Updated by okurz 4 months ago

For SUSE QE maintenance tests we already have a mailing list qa-maintenance-reports@suse.de that receives comments from https://gitlab.suse.de/qa-maintenance/openQABot/ on build.suse.de whenever any incident related tests fail. The archive can be seen on
http://mailman.suse.de/mlarch/SuSE/qa-maintenance-reports/index.html

Also available in: Atom PDF