[libvirt PATCH v2 09/10] docs: ci: Add a section on how to add a new platform to libvirt CI

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx>
---
 docs/ci.rst | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/ci.rst b/docs/ci.rst
index 566bc42db7..efb1ea295e 100644
--- a/docs/ci.rst
+++ b/docs/ci.rst
@@ -40,3 +40,12 @@ Retrieving test logs
 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).
+
+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>`__
-- 
2.36.1




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux