On Thu, Jun 11, 2020 at 12:03:08PM +0200, Andrea Bolognani wrote: > The ci-* targets need to know where our container images are stored > and how they are called to work, so now that we use the GitLab > container registry instead of Quay some changes are necessary. > > Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> > --- > ci/Makefile | 10 +++++----- > ci/list-images.sh | 24 ++++++------------------ > 2 files changed, 11 insertions(+), 23 deletions(-) > > diff --git a/ci/Makefile b/ci/Makefile > index bc1dac11e3..dc8012f33b 100644 > --- a/ci/Makefile > +++ b/ci/Makefile > @@ -50,11 +50,11 @@ CI_BUILD_SCRIPT = $(CI_ROOTDIR)/build.sh > # Location of the container images we're going to pull > # Can be useful to overridde to use a locally built > # image instead > -CI_IMAGE_PREFIX = quay.io/libvirt/buildenv-libvirt- > +CI_IMAGE_PREFIX = registry.gitlab.com/libvirt/libvirt/ci- > > -# The default tag is ':latest' but if the container > +# The default tag is ':master' but if the container > # repo above uses different conventions this can override it > -CI_IMAGE_TAG = :latest > +CI_IMAGE_TAG = :master Drop this since we went back to latest Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
