792843c05e
Since the string "ci" is already contained in the path, it seems unnecessary to include it into the filename too: in fact, we only do that for Dockerfiles and not for files in ci/cirrus, even though those are generated the very same way. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com> |
||
|---|---|---|
| .. | ||
| centos-7.Dockerfile | ||
| centos-8.Dockerfile | ||
| centos-stream.Dockerfile | ||
| debian-10-cross-aarch64.Dockerfile | ||
| debian-10-cross-armv6l.Dockerfile | ||
| debian-10-cross-armv7l.Dockerfile | ||
| debian-10-cross-i686.Dockerfile | ||
| debian-10-cross-mips64el.Dockerfile | ||
| debian-10-cross-mips.Dockerfile | ||
| debian-10-cross-mipsel.Dockerfile | ||
| debian-10-cross-ppc64le.Dockerfile | ||
| debian-10-cross-s390x.Dockerfile | ||
| debian-10.Dockerfile | ||
| debian-sid-cross-aarch64.Dockerfile | ||
| debian-sid-cross-armv6l.Dockerfile | ||
| debian-sid-cross-armv7l.Dockerfile | ||
| debian-sid-cross-i686.Dockerfile | ||
| debian-sid-cross-mips64el.Dockerfile | ||
| debian-sid-cross-mipsel.Dockerfile | ||
| debian-sid-cross-ppc64le.Dockerfile | ||
| debian-sid-cross-s390x.Dockerfile | ||
| debian-sid.Dockerfile | ||
| fedora-32.Dockerfile | ||
| fedora-33.Dockerfile | ||
| fedora-rawhide-cross-mingw32.Dockerfile | ||
| fedora-rawhide-cross-mingw64.Dockerfile | ||
| fedora-rawhide.Dockerfile | ||
| opensuse-152.Dockerfile | ||
| README.rst | ||
| ubuntu-1804.Dockerfile | ||
| ubuntu-2004.Dockerfile | ||
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