Allow to auto start some deployments via cross repo pipelines
What does this MR do and why?
Change deployment rules so we can have some deployments auto starting during cross repo.
- if: '$CI_PIPELINE_SOURCE == "pipeline" && $CI_JOB_NAME =~ $DEPLOYMENT_FLAVOR'
- if: '$CI_PIPELINE_SOURCE == "pipeline"'
allow_failure: true
when: manual
If deployment flavor is passed via the cross-repo pipeline, the job with matching name will start automatically and are not allowed to failed Others job will be in manual and allowed to failed
This could be useful for allowing renovate to start some deployments (capd / capm3?) in order to validate that some changes in sylva-elements are not breaking anything before automerging them
eg: sylva-projects/sylva-elements/sylvactl!172 (merged) For sylvactl we could allow renovate to automerge some MR (eg GO modules patches updates) if we have a green CI (including a capd / capm3 deployments)
Related reference(s)
Edited by Loic Nicolle