ci: Prepare CI/CD rules for Merge Train
What does this MR do and why?
This implements the proposal from gitlab-org/quality/quality-engineering/team-tasks#195 (comment 1135174543) in preparation of experimenting with Merge Train.
I mostly replaced $CI_MERGE_REQUEST_IID
with ($CI_MERGE_REQUEST_EVENT_TYPE == "merged_result" || $CI_MERGE_REQUEST_EVENT_TYPE == "detached")
, in order to keep the same behavior but explicitely exclude Merge Train events (but filtering on the allowed events to be either merged_result
or detached
).
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Rémy Coutable