mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-11-08 14:29:56 +00:00
34f62f8ecb
The corresponding libvirt-ci commit is: commit 512b1011559165e3f37eae675dd43a431b95baa3 projects: install clang on Linux Signed-off-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Neal Gompa <ngompa13@gmail.com> |
||
---|---|---|
.. | ||
libvirt-centos-7.Dockerfile | ||
libvirt-centos-8.Dockerfile | ||
libvirt-centos-stream.Dockerfile | ||
libvirt-debian-10-cross-aarch64.Dockerfile | ||
libvirt-debian-10-cross-armv6l.Dockerfile | ||
libvirt-debian-10-cross-armv7l.Dockerfile | ||
libvirt-debian-10-cross-i686.Dockerfile | ||
libvirt-debian-10-cross-mips64el.Dockerfile | ||
libvirt-debian-10-cross-mips.Dockerfile | ||
libvirt-debian-10-cross-mipsel.Dockerfile | ||
libvirt-debian-10-cross-ppc64le.Dockerfile | ||
libvirt-debian-10-cross-s390x.Dockerfile | ||
libvirt-debian-10.Dockerfile | ||
libvirt-debian-sid-cross-aarch64.Dockerfile | ||
libvirt-debian-sid-cross-armv6l.Dockerfile | ||
libvirt-debian-sid-cross-armv7l.Dockerfile | ||
libvirt-debian-sid-cross-i686.Dockerfile | ||
libvirt-debian-sid-cross-mips64el.Dockerfile | ||
libvirt-debian-sid-cross-mipsel.Dockerfile | ||
libvirt-debian-sid-cross-ppc64le.Dockerfile | ||
libvirt-debian-sid-cross-s390x.Dockerfile | ||
libvirt-debian-sid.Dockerfile | ||
libvirt-fedora-31.Dockerfile | ||
libvirt-fedora-32.Dockerfile | ||
libvirt-fedora-rawhide-cross-mingw32.Dockerfile | ||
libvirt-fedora-rawhide-cross-mingw64.Dockerfile | ||
libvirt-fedora-rawhide.Dockerfile | ||
libvirt-opensuse-151.Dockerfile | ||
libvirt-ubuntu-1804.Dockerfile | ||
libvirt-ubuntu-2004.Dockerfile | ||
README.rst | ||
refresh |
CI job assets
This directory contains assets used in the automated CI jobs, most notably the Dockerfiles used to build container images in which the CI jobs then run.
The refresh
script is used to re-create the Dockerfiles using the lcitool
command that is provided by repo https://gitlab.com/libvirt/libvirt-ci
The containers are built during the CI process and cached in the GitLab container registry of the project doing the build. The cached containers can be deleted at any time and will be correctly rebuilt.