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>
---
docs/ci.rst | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/docs/ci.rst b/docs/ci.rst
index 2e88e06b1b..b321a67bd9 100644
--- a/docs/ci.rst
+++ b/docs/ci.rst
@@ -4,10 +4,14 @@ Libvirt Continuous Integration
.. contents::
-The libvirt project primarily uses GitLab CI for automated testing of Linux
-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>`_
-is temporarily used for validating FreeBSD builds.
+The libvirt project uses GitLab CI for automated testing.
+
+Linux builds and cross-compiled Windows builds happen on GitLab CI's shared
+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
===================
--
2.25.4