a79ac43f04
Leap 15.1 will reach EOL on January 31st 2021, so we should not test on it during the current development cycle ending on March 1st. Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .. | ||
| ci-centos-7.Dockerfile | ||
| ci-centos-8.Dockerfile | ||
| ci-centos-stream.Dockerfile | ||
| ci-debian-10-cross-aarch64.Dockerfile | ||
| ci-debian-10-cross-armv6l.Dockerfile | ||
| ci-debian-10-cross-armv7l.Dockerfile | ||
| ci-debian-10-cross-i686.Dockerfile | ||
| ci-debian-10-cross-mips64el.Dockerfile | ||
| ci-debian-10-cross-mips.Dockerfile | ||
| ci-debian-10-cross-mipsel.Dockerfile | ||
| ci-debian-10-cross-ppc64le.Dockerfile | ||
| ci-debian-10-cross-s390x.Dockerfile | ||
| ci-debian-10.Dockerfile | ||
| ci-debian-sid-cross-aarch64.Dockerfile | ||
| ci-debian-sid-cross-armv6l.Dockerfile | ||
| ci-debian-sid-cross-armv7l.Dockerfile | ||
| ci-debian-sid-cross-i686.Dockerfile | ||
| ci-debian-sid-cross-mips64el.Dockerfile | ||
| ci-debian-sid-cross-mipsel.Dockerfile | ||
| ci-debian-sid-cross-ppc64le.Dockerfile | ||
| ci-debian-sid-cross-s390x.Dockerfile | ||
| ci-debian-sid.Dockerfile | ||
| ci-fedora-32.Dockerfile | ||
| ci-fedora-33.Dockerfile | ||
| ci-fedora-rawhide-cross-mingw32.Dockerfile | ||
| ci-fedora-rawhide-cross-mingw64.Dockerfile | ||
| ci-fedora-rawhide.Dockerfile | ||
| ci-opensuse-152.Dockerfile | ||
| ci-ubuntu-1804.Dockerfile | ||
| ci-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.
Coverity scan integration
This will be used only by the main repository for master branch by running scheduled pipeline in GitLab.
The service is proved by Coverity Scan and requires that the project is registered there to get free coverity analysis which we already have for libvirt project.
To run the coverity job it requires two new variables:
COVERITY_SCAN_PROJECT_NAME, containing the libvirt project name.COVERITY_SCAN_TOKEN, token visible to admins of libvirt project