action #133328
Updated by okurz over 1 year ago
## Motivation Often we have broken gitlab CI pipelines which cause a shitload of notification emails which make people go into alert fatigue pretty quickly. jbaier recently disabled email notifications for selected projects as long as there were known issues to be fixed infra-wise. Maybe we can find a single-command that we can execute in such cases to disable all "relevant" project's notifications and then enable again. ## Acceptance criteria * **AC1:** progress.opensuse.org/projects/qa/wiki/tools#Alert-handling mentions a feasible way how to disable/enable gitlab CI notifications for osd-admins@suse.de email notifications ## Suggestions * See how it already works over the GUI, e.g. on https://gitlab.suse.de/openqa/salt-states-openqa/edit, go to "Visibility, project features, permissions" and at the bottom of the section there is a checkbox "Disable email notifications". That's the one * Lookup https://docs.gitlab.com/ee/api/notification_settings.html or related APIs as we know it's possible to do over the GUI and come up with a fancy bash-for-loop curl based API call or something with the input of a list of common projects and controlling any notifications to osd-admins@suse.de (not the individual users) * Maybe it's possible to query "all projects which have osd-admins@suse.de in email-notifications" otherwise hard-code a list * Add to progress.opensuse.org/projects/qa/wiki/tools#Alert-handling ## Further details * This is not about personal notification subscriptions to git projects but about gitlab CI email notifications to osd-admins@suse.de only * It's ok if the email notifications are disabled for all subscribed email addresses, not only osd-admins@suse.de