libvirt/ci/containers/refresh
Andrea Bolognani 95abbdc432 ci: Use GitLab container registry
Instead of using pre-built containers hosted on Quay, build
containers as part of the GitLab CI pipeline and upload them to the
GitLab container registry for later use.

This will not significantly slow down builds, because containers are
only rebuilt when the corresponding Dockerfile has been modified.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2020-06-11 19:06:51 +02:00

42 lines
891 B
Bash
Executable File

#!/bin/sh
if test -z "$1"
then
echo "syntax: $0 PATH-TO-LCITOOL"
exit 1
fi
LCITOOL=$1
if ! test -x "$LCITOOL"
then
echo "$LCITOOL is not executable"
exit 1
fi
HOSTS=$($LCITOOL hosts | grep -v freebsd)
for host in $HOSTS
do
case "$host" in
libvirt-fedora-rawhide)
for cross in mingw32 mingw64
do
$LCITOOL dockerfile $host libvirt --cross $cross >$host-cross-$cross.Dockerfile
done
;;
libvirt-debian-*)
for cross in aarch64 armv6l armv7l i686 mips mips64el mipsel ppc64le s390x
do
if test "$host" = "libvirt-debian-9" && test "$cross" = "i686"
then
continue
fi
$LCITOOL dockerfile $host libvirt --cross $cross >$host-cross-$cross.Dockerfile
done
;;
esac
$LCITOOL dockerfile $host libvirt >$host.Dockerfile
done