Cope with S1 bugs without a group
requested to merge 1143-builds-gitlab-org-quality-triage-ops-lib-shared-resource_group-rb-53-in into master
What does this MR do and why?
In the rare cases where S1 don't have a group label, the automation shouldn't break on it.
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-with-a-dry-run on how to perform dry-runs.
Action items
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-
Closes #1143 (closed)
Edited by Rémy Coutable