Apply the `latest` tag in a more consistent way (!162) · Merge requests · infrastructure / apertis-docker-images

Merged Emanuele Aina requested to merge wip/em/make-latest-tagging-consistent into apertis/v2022dev1 4 years ago

Jan 15, 2021

gilab-ci: Apply all `latest` tags once everything else succeeded · 2dc096d6

Emanuele Aina authored 4 years ago


By applying `latest` tags as soon as the relevant image has been built
we end up with a quite large time window where they are all quite out
of sync: in particular, the tag is applied to the `base` image as soon
as it is ready, before all the depending images get built.

On top of that, if depending images fail, the `latest` tags will stay
out of sync.

This can be quite confusing for users, so let's apply the `latest` tag
only after all the previous stages have completed.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

2dc096d6

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

Emanuele Aina authored 4 years ago


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 <emanuele.aina@collabora.com>

aa6fd73d

Apply the `latest` tag in a more consistent way

Merge request reports

Activity