Skip to content

Do not allow package promotion before gprd-cny deployment

Alessio Caiazza requested to merge promote_after_successfull_deployment into master

What does this MR do and why?

I was extracting some data from the pipeline APIs and I found out that is really hard to identify failed pipelines.

Because the promote job is manual and only requires the auto_deploy:start job, when a deployment failure happens before the promotion, a pipeline is marked as blocked (manual on the API) instead of failed

Pipeline 1219431 is an example

image

With this change, the promote job will not be available before a successful gprd-cny deployment, marking the pipeline with the correct status, and preventing us from accidentally promoting a package that failed on previous environments.

Author Check-list

  • Has documentation been updated?
Edited by Alessio Caiazza

Merge request reports