Skip to content
Snippets Groups Projects
Commit aa6fd73d authored by Emanuele Aina's avatar Emanuele Aina
Browse files

gitlab-ci: Ensure that `latest` tag comes from the latest pipeline


We want to ensure that the jobs updating the `latest` tags always reflect
the actual latest pipeline.

When two pipelines are started at the same time on the same branch
sometimes the earlier one can complete last due to scheduling or any
other reason, thus breaking the previous assumption.

To avoid that, make the whole pipeline interruptible up to the tagging jobs
so that earlier pipelines get killed when a new one is started.

Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
parent 70760d90
No related branches found
No related tags found
2 merge requests!162Apply the `latest` tag in a more consistent way,!93WIP: documentation-builder: Rebase on Apertis instead of Debian Buster
......@@ -12,6 +12,15 @@ variables:
STABLE: auto
TEST_TAG: test-${CI_PIPELINE_ID}
default:
# we want to ensure that the jobs updating the `latest` tags always reflect
# the actual latest pipeline. when two pipelines are started at the same time
# on the same branch sometimes the earlier one can complete last due to
# scheduling or any other reason, thus breaking the previous assumption.
# to avoid that, make the whole pipeline interruptible up to the tagging jobs
# so that earlier pipelines get killed when a new one is started
interruptible: true
before_script:
- |
if [ "${CI_COMMIT_BRANCH%%/*}" = "$DISTRO" ]
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment