Since update to 14.6: On duplicate pipelines, the merge request pipeline is no longer used to determine mergeability
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
When upgrading from 14.5.2 to 14.6.1 the behaviour, which pipeline is used to determine mergeability, was changed.
Steps to reproduce
(We) have 2 pipelines:
- a branch pipeline (in our case for manual deployment) configured with
only: refs: branches - a (detached) merge request pipeline (in our case for running tests) configured with
only: refs: merge_requests
The branch pipeline is referenced in the merge request.
What is the current bug behavior?
Before the upgrade to 14.6.(1) we were running 14.5.2 and it was always the (second/newer) detached merge request pipeline which was relevant for the "calculation" if the merge request is mergeable or not.
After the upgrade to 14.6.(1) it is always the branch pipeline. This is highly problematic because the merge requests pipeline should be the relevant one. (E.g. tests can fail and the merge request is still mergeable.)
What is the expected correct behavior?
In my opinion: The behaviour from 14.5.2, relevant for the merge request is before everything the merge request pipeline. Use the branch pipeline only in case there is no merge request pipeline configured.