docs: Update CI documentation

We're no longer using either Travis CI or the Jenkins-based
CentOS CI, but we have started using Cirrus CI.

Mention the libvirt-ci subproject as well, as a pointer for those
who might want to learn more about our CI infrastructure.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Andrea Bolognani 2020-07-02 15:02:38 +02:00
parent fb91290131
commit c203b8fee1

View File

@ -4,10 +4,14 @@ Libvirt Continuous Integration
.. contents:: .. contents::
The libvirt project primarily uses GitLab CI for automated testing of Linux The libvirt project uses GitLab CI for automated testing.
builds, and cross-compiled Windows builds. `Travis <https://travis-ci.org/libvirt/libvirt>`_
is used for validating macOS builds, and `Jenkins <https://ci.centos.org/view/libvirt>`_ Linux builds and cross-compiled Windows builds happen on GitLab CI's shared
is temporarily used for validating FreeBSD builds. runners, while FreeBSD and macOS coverage is achieved by triggering `Cirrus CI
<https://cirrus-ci.com/>`_ jobs behind the scenes.
Most of the tooling used to build CI pipelines is maintained as part of the
`libvirt-ci <https://gitlab.com/libvirt/libvirt-ci>`_ subproject.
GitLab CI Dashboard GitLab CI Dashboard
=================== ===================