Skip to content

Support stages from policies with override_project_ci strategy

Martin Čavojrequested to merge
494431-job-with-custom-stage-not-included-in-pipeline-enforced-via-pipeline-execution-policy into master

What does this MR do and why?

Support stages from policies with override_project_ci strategy.

If there is a pipeline execution policy with strategy override_project_ci, we use its declared stages when we inject jobs.

If there are multiple override_project_ci policies, the stages must be matching - all stages must be a subset of the largest stages set.

Depends on Refactor PEP using PipelineContext (!172295 - merged).

References

Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

  1. Create a project
  2. Create a pipeline execution policy with override_project_ci strategy
  3. In the policy CI YAML, use a non-standard stage such as policy-test
  4. Run the pipeline and verify that jobs using policy-test stage are present in the pipeline

Related to #494431 (closed)

Edited by Martin Čavoj

Merge request reports