Project

General

Profile

action #103602

Reply to gitlab@suse.de pipeline email fails silently

Added by cdywan about 2 months ago. Updated about 1 month ago.

Status:
Blocked
Priority:
Low
Assignee:
Target version:
Start date:
2021-12-07
Due date:
% Done:

0%

Estimated time:

Description

Observation

When I check emails for broken pipelines on GitLab, like for other notification emails, I typically respond by pasting a ticket URL. Except nothing happens when I do that with failed GitLab pipelines.

Acceptance criteria

  • AC1: Responses to failed pipeline emails are handled

Suggestions

  • Maybe this never worked and nobody noticed the missing emails?
    • I remember one time this year Nick told me that he didn't see my email because we were talking on jitsi, but at the time it was assumed to be a fluke
  • Investigate why gitlab@suse.de doesn't respond with an error either
  • Find out where this is configured
  • Check upstream docs

History

#2 Updated by okurz about 2 months ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Priority changed from Normal to Low
  • Target version set to Ready

#3 Updated by cdywan about 2 months ago

okurz wrote:

I updated the wiki https://progress.opensuse.org/projects/qa/wiki/Wiki/diff?utf8=%E2%9C%93&version=381&version_from=380&commit=View+differences to clarify that gitlab@suse.de swallows emails into the void. Reported a ticket https://sd.suse.com/servicedesk/customer/portal/1/SD-69703

Thanks!

Please also share the ticket so others can see it.

#4 Updated by tinita about 2 months ago

I usually hit "reply" and then replace the To field with the osd-admins address.

#5 Updated by okurz about 1 month ago

SD ticket was delegated to https://jira.suse.com/browse/ENGINFRA-1016 , blocking on that

Also available in: Atom PDF