Introduce a processor to manage pipeline failures
requested to merge 1291-port-the-existing-pipeline-failure-tooling-from-gitlab-org-gitlab into master
What does this MR do and why?
This introduces a new PipelineFailureManagement
processor that should be able to replace the tooling we currently have in the gitlab-org/gitlab
project.
For now, the processor will only be enabled on the sandbox project to ensure it works as expected.
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 for new policies.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(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 #1291 (closed)
Edited by Rémy Coutable