Actions
action #110629
closedQA - 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
openqa-label-known-issues: Fallback notification address in openqa-label-known-issues if no email address could be parsed from group_overview
Description
Motivation¶
openqa-label-known-issues can inform about "unknown, to be reviewed issues". For this in #91605 we added support to send messages to configured email addresses in openQA job group descriptions. If no such email address is configured then we would loose the information about "unknown, to be reviewed issue". Instead we could, if configured, send a message to a "catch-all" address.
Acceptance criteria¶
- AC1: Given a catch-all address configured, e.g. by environment variable configured in /etc/openqa/openqa.ini on the job done hook configuration line, When an unknown issue is encountered by openqa-label-known-issue And no email address could be parsed from the according openQA job group, Then send to the catch-all address instead
- AC2: Given no catch-all address configured, When (as in AC1) Then the message about unknown issue is discarded (or logged)
Suggestions¶
- Add elif branch to https://github.com/os-autoinst/scripts/blob/master/_common#L112= if catch-all address configured and send to that instead
- Optional: Already configure catch-all addresses for o3 and/or osd, e.g. a dedicated mailing list or chat channel and inform people about that "triaging" channel. Every message to that channel would mean that the according openQA job should be reviewed and at least labeled accordingly and a proper communication target should be provided within the according job group
Actions