Notify failed master pipeline status in merge requests if the merge request can potentially be blocked by the same failures
Proposal
Suggested in gitlab-org/quality/engineering-productivity/team#419 (comment 1806203314)
create a new
triage-ops
processor that would act when a pipeline finishes, to update the latest status of each job (we should also store thefinished_at
of jobs in the JSON status file) so that we only update the status iffinished_at
is> existing_status finished_at
Context
we would like to capture the statuses of gitlab master pipeline jobs in a status page, and use this information to decide if a full pipeline after MR approval
should run, or cancel if a full pipeline is triggered.
Action Plan
- create a master pipeline jobs status page
- allow triage-ops to update the status page by reacting to succeeded/failed master pipelines
-
Maybe in different processor, automatically cancel pipeline if status page indicates a broken master pipelineWith Danger, alert MR if pipeline is likely blocked by a broken master pipeline. Optional: fail the Danger job if the blocker master pipeline is detected - update the new_pipeline_on_approval processor to check the status page before triggering pipeline.
Edited by Jennifer Li