Skip to content

Fix pipelines status detection for auto-deploy

What does this MR do and why?

Describe in detail what your merge request does and why.

When checking our package distribution I noticed a pattern where we have some packages available both at 00 and 15 minutes without any pick into auto-deploy.

Debugging those pipelines I figured out that now that we tag right after generating the branch it is possible for the pipeline to still be in the created state if GitLab.com is under heavy load.

This merge request will consider the created state like the running state.

Author Check-list

  • Has documentation been updated?

Merge request reports