Actions
action #17252
openQA - coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release
coordination #99306: [epic] Future improvements: Make reviewing openQA results per squad easier
notifications to maintainer on failed modules
Start date:
2016-02-09
Due date:
% Done:
0%
Estimated time:
Tags:
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
Actions