2020-05-04 12:15:43 +00:00
|
|
|
==============================
|
|
|
|
|
Libvirt Continuous Integration
|
|
|
|
|
==============================
|
|
|
|
|
|
|
|
|
|
.. contents::
|
|
|
|
|
|
2020-07-02 13:02:38 +00:00
|
|
|
The libvirt project uses GitLab CI for automated testing.
|
2022-07-12 11:15:07 +00:00
|
|
|
`Here's <ci-dashboard.html>`__ our CI dashboard which shows the current status
|
|
|
|
|
of our pipelines.
|
2020-07-02 13:02:38 +00:00
|
|
|
|
2022-07-12 11:19:14 +00:00
|
|
|
Builds and unit tests
|
|
|
|
|
=====================
|
|
|
|
|
|
2020-07-02 13:02:38 +00:00
|
|
|
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.
|
2020-05-04 12:15:43 +00:00
|
|
|
|
2022-07-12 11:19:14 +00:00
|
|
|
Integration tests
|
|
|
|
|
=================
|
2020-05-04 12:15:43 +00:00
|
|
|
|
2022-07-12 11:19:14 +00:00
|
|
|
Integration tests in our CI pipelines require dedicated HW which is not
|
|
|
|
|
available to forks, see `GitLab CI Custom Runners <ci-runners.html>`__.
|
|
|
|
|
Therefore, in order to execute the integration tests as part of your libvirt
|
|
|
|
|
fork's GitLab CI you'll need to provide your own runner. You'll also need to
|
|
|
|
|
set a few CI variables to run the integration tests as part of the CI pipeline,
|
|
|
|
|
see below.
|
2020-05-04 12:15:43 +00:00
|
|
|
|
2022-07-12 11:19:14 +00:00
|
|
|
GitLab CI variables
|
|
|
|
|
-------------------
|
2020-05-04 12:15:43 +00:00
|
|
|
|
2023-09-27 08:38:57 +00:00
|
|
|
* ``LIBVIRT_CI_INTEGRATION`` - enables integration test suite execution as part
|
|
|
|
|
of the pipeline (works in forks too if there's a registered shared runner)
|
|
|
|
|
* ``LIBVIRT_CI_INTEGRATION_RUNNER_TAG`` - overrides the gitlab-runner tag for
|
|
|
|
|
the pipeline; this is needed in forks because the default tag only matches
|
|
|
|
|
upstream shared runners which may be (and will be) different from the tags
|
|
|
|
|
defined on shared runners in forks
|
2020-05-04 12:15:43 +00:00
|
|
|
|
2022-07-12 11:19:14 +00:00
|
|
|
Retrieving test logs
|
|
|
|
|
--------------------
|
2020-05-04 12:15:43 +00:00
|
|
|
|
2022-07-12 11:19:14 +00:00
|
|
|
In case the integration test suite fails in our CI pipelines, a job artifact is
|
|
|
|
|
generated containing Avocado logs, libvirt debug logs, and the latest traceback
|
|
|
|
|
(if one was produced during a daemon's execution).
|
2022-07-12 11:44:26 +00:00
|
|
|
|
|
|
|
|
Adding new OS platforms OR build pre-requisites
|
|
|
|
|
===============================================
|
|
|
|
|
|
|
|
|
|
Since all of the Dockerfiles libvirt uses for CI have been generated by ``lcitool``
|
|
|
|
|
provided by the `libvirt-ci <https://gitlab.com/libvirt/libvirt-ci.git>`__ project,
|
|
|
|
|
most relevant changes will need to be introduced to ``lcitool`` first. Please
|
|
|
|
|
follow the instructions outlined
|
|
|
|
|
`here <https://gitlab.com/libvirt/libvirt-ci/-/blob/master/docs/platforms_and_mappings.rst>`__
|
2022-07-12 11:44:53 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
Running CI workloads locally
|
|
|
|
|
============================
|
|
|
|
|
|
|
|
|
|
If you're interested in running the CI test workloads locally, please read
|
|
|
|
|
our `testing <testing.html>`__ guide.
|
