aboutsummaryrefslogtreecommitdiff
path: root/setup.py
diff options
context:
space:
mode:
authorDaniel P. Berrangé <berrange@redhat.com>2023-02-21 17:48:50 +0000
committerDaniel P. Berrangé <berrange@redhat.com>2023-02-22 15:25:58 +0000
commit6e3c5ccac77714be70c0dc52c5210c7cda8fe40f (patch)
tree3d1a8fb71aadb9c466225b59466be8b9de7f0dc6 /setup.py
parentfd0b464e3441f778a8fd977501ceeb4e98bc99f0 (diff)
downloadlibvirt-ci-6e3c5ccac77714be70c0dc52c5210c7cda8fe40f.zip
libvirt-ci-6e3c5ccac77714be70c0dc52c5210c7cda8fe40f.tar.gz
libvirt-ci-6e3c5ccac77714be70c0dc52c5210c7cda8fe40f.tar.bz2
containers: publish to 'latest' tag instead of 'master'
Historically we use the CI_COMMIT_REF_SLUG for the docker tag, which is the branch name. This meant that when testing container builds from non-default tags/branches we didn't pollute the primary published content. When we switched to use merge requests for triggering CI in: commit 7a7402d259db6e75b2a6fbb1523b42a2d18fabfa Author: Daniel P. Berrangé <berrange@redhat.com> Date: Thu Feb 10 17:43:56 2022 +0000 gitlab: switch to trigger jobs against the merge request by default we stopped publishing containers for anything except a push to the default branch. As such there's no reason to use CI_COMMIT_REF_SLUG, we can just use a fixed tag name. The docker default is to use ':latest', so adopt that instead of ':master'. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Diffstat (limited to 'setup.py')
0 files changed, 0 insertions, 0 deletions