'Pipelines must succeed' setting should also apply to branch pipelines
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
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.
Use Cases
- External integrations: Third-party security scanners or CI tools that create branch pipelines
- Compliance requirements: Organizations need all security/compliance checks to pass
- Mixed workflows: Teams running different job sets in branch vs. merge request pipelines
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.
Edited by Rutvik Shah