Skip to content

Draft: Add setting to consider non-existent pipelines successful

Hordur Freyr Yngvason requested to merge track-mr-ci-config-processing into master

What does this MR do and why?

This adds a new project setting under the "Pipelines must succeed" section, called "Pipelines must exist". It defaults to true, but when false, the CI mergeability check considers non-existent pipelines successful. This is useful for when pipelines are intentionally filtered out by workflow:rules or individual job rules, and is generally a sound default for projects that don't rely on external CI or similar.

To accomplish this, we keep track of the source branch SHA corresponding to the latest processed CI configuration of each merge request, regardless of whether a pipeline was created or not.

This will have other benefits, outside of "Pipelines must succeed", such as allowing us to not display the MR pipeline spinner when we know the latest pipeline configuration has been processed.

See #334281

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Hordur Freyr Yngvason

Merge request reports