mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-10-16 11:09:24 +00:00
95abbdc432
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>
15 lines
540 B
ReStructuredText
15 lines
540 B
ReStructuredText
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.
|