Hint about how we retry one-off policies
What does this MR do and why?
It's not unusual that I have to retry several times to fully completely running one-off policies. However, it's a new record that it took so many times that I ended up with modifying the script to do so.
This documents how that's done.
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
-
Edited by Lin Jen-Shin