Project

General

Profile

Actions

action #95188

closed

Document how to properly configure GitLab pipeline notifications size:M

Added by livdywan almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Organisational
Target version:
Start date:
2021-07-07
Due date:
2021-09-01
% Done:

0%

Estimated time:

Description

Observation

Team members don't reliably get notifications for pipelines such as osd-deployment, but also others. Some suggestions have come up in conversations but it's not clear exactly how to configure it and trivial suggestions don't seem to be fruitful.

Acceptance criteria

  • AC1: Wiki page explains how to get reliable notifications

Out of scope

  • Works for everyone in the team.
  • Non specific kind of messages.

Suggestions


Related issues 1 (0 open1 closed)

Related to openQA Project - action #95105: osd-deployment pipelines fail and alerts are not handled size:MResolvedlivdywan2021-07-062021-07-08

Actions
Actions #1

Updated by okurz almost 3 years ago

I think https://stackoverflow.com/questions/46472631/notify-all-group-members-of-failed-pipelines-in-gitlab describes the problem … and a good solution

we should just configure gitlab to send emails to osd-admins@suse.de for all projects if that is possible.

Actions #2

Updated by okurz almost 3 years ago

  • Related to action #95105: osd-deployment pipelines fail and alerts are not handled size:M added
Actions #4

Updated by mkittler almost 3 years ago

The previous comment is actually from me. So far I've only got a mail "Successful pipeline for master | osd-deployment | af090d3d" and that although I've checked "Notify only broken pipelines". So I am not sure yet whether it worked.

Actions #5

Updated by mkittler almost 3 years ago

Yesterday I've received "Failed pipeline for master | osd-deployment | af090d3d" which says "Pipeline #168676 triggered by Oliver Kurz" so I guess it worked.

Actions #6

Updated by ilausuch almost 3 years ago

  • Subject changed from Document how to properly configure GitLab pipeline notifications to Document how to properly configure GitLab pipeline notifications size: M
  • Description updated (diff)
Actions #7

Updated by ilausuch almost 3 years ago

  • Status changed from New to Workable
Actions #8

Updated by okurz almost 3 years ago

  • Subject changed from Document how to properly configure GitLab pipeline notifications size: M to Document how to properly configure GitLab pipeline notifications size:M
Actions #9

Updated by tinita over 2 years ago

I added osd-admins@suse.de to https://gitlab.suse.de/openqa/osd-deployment/-/services/pipelines_email/edit

This was suggested over a month ago, but nobody did it.

Actions #12

Updated by livdywan over 2 years ago

  • Status changed from Workable to Feedback
  • Assignee set to tinita

We discussed this in the daily. Let's see if either the ml, .de or .com emails work.

Actions #13

Updated by tinita over 2 years ago

Personal emails seem to work, but the list doesn't work because gitlab@suse.de is not allowed to write to the list.

Not sure who is the owner, so I wrote an email to osd-admins-owner@suse.de

Actions #14

Updated by okurz over 2 years ago

As owner of osd-admins I now added gitlab@suse.de as valid sender. You confirmed to have received according emails already.

Actions #15

Updated by tinita over 2 years ago

okurz wrote:

As owner of osd-admins I now added gitlab@suse.de as valid sender. You confirmed to have received according emails already.

I received an email today (friday) at 05:58:57 Failed pipeline for master | osd-deployment | 4e4ecc88 to my personal address. But nothing arrived at the list so far.

Actions #16

Updated by okurz over 2 years ago

See related #97406

Actions #17

Updated by okurz over 2 years ago

From mailman:

The osd-admins@suse.de mailing list has 2 request(s) waiting for your
consideration at:

    http://mailman.suse.de/mailman/admindb/osd-admins

Please attend to this at your earliest convenience.  This notice of
pending requests, if any, will be sent out daily.


Pending posts:
From: gitlab@suse.de on Fri Aug 20 05:58:57 2021
Subject: Failed pipeline for master | osd-deployment | 4e4ecc88
Cause: Message has implicit destination

From: gitlab@suse.de on Mon Aug 23 05:57:27 2021
Subject: Failed pipeline for master | osd-deployment | 4e4ecc88
Cause: Message has implicit destination

so we would need to learn if we can configure mailman to accept that. gitlab has it explicitly selected to use BCC (or CC) to send the emails to.

Following https://support.tigertech.net/mailman-implicit-destination I have on https://mailman.suse.de/mailman/admin/osd-admins/privacy/recipient changed "Must posts have list named in destination (to, cc) field (or be among the acceptable alias names, specified below)?" from "Yes" to "No"

If this does not work then what I also tried is to create a proper IDP account for "osd-admins@suse.de" following the create users page from https://bugzilla.suse.com with username "osd-admins", same password as the admin password for the mailing list, and then trying to login on https://gitlab.suse.de/users/sign_in . But this failed so far. Maybe takes some time to sync. If we can login maybe "osd-admins" can take over the pipeline. I also put the password into https://gitlab.suse.de/openqa/scripts/-/commit/359f4a9a67634f70dcb35b5f429f8fe5c7fb0356

Actions #18

Updated by okurz over 2 years ago

  • Due date set to 2021-09-01
Actions #19

Updated by tinita over 2 years ago

Currently osd-admins@suse.de is listed as a recipient in the Pipeline status emails of the following projects:

I added this to the Wiki:
https://progress.opensuse.org/projects/qa/wiki/Wiki#section-22

I couldn't find any other projects with scheduled pipelines.
Let me know if there are projects which should be added.

Otherwise the ticket can be resolved I think.

Actions #20

Updated by okurz over 2 years ago

As far as ACs this looks good because the wiki describes what to do. However there are some important projects that immediately come to mind:

  • openqa/salt-pillars-openqa
  • openqa/auto-review
  • openqa/grafana-webhook-actions
  • qa-maintenance/openQABot
  • qa-maintenance/bot-ng

I might have mistyped from memory. These should be handled

Actions #21

Updated by tinita over 2 years ago

Ok, I added the projects suggested by @okurz and updated the wiki

Actions #22

Updated by okurz over 2 years ago

  • Status changed from Feedback to Resolved

very nice. I think this is more than enough right now. Thanks a lot!

Actions

Also available in: Atom PDF