'Pipelines must succeed' setting should also apply to branch pipelines
Problem
As a DevOps engineer with an external integration, I want all pipelines to be successful/checked for success before merge, so that I can be confident all compliance/security checks are done.
In addition if both branch
and merge request
pipelines run today it's a race to see which one will be the primary
pipeline for the merge request to allow merge.
Proposal
Add a setting to choose which pipeline / both latest pipelines must be successful if a project is setup to run both pipelines. - This might be the case for external service checks like a security tool running in its own branch pipeline.
Additional use case/details
A 450 seats silver customer would like to have Pipelines must succeed
setting honour all/branch pipelines associated with a merge request.
Currently, this check is performed only for the latest merge request pipelines. Customer proposes to have a new option: All pipeline types
under Settings -> Merge requests -> Merge checks -> Pipelines must succeed setting. If this option is enabled and the latest branch pipeline is in failed state (even if merge request pipeline is successful), merge should be blocked.