[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v3 04/36] docs/devel: remind developers to run CI container pipel
From: |
Alex Bennée |
Subject: |
[PATCH v3 04/36] docs/devel: remind developers to run CI container pipeline when updating images |
Date: |
Tue, 27 Jun 2023 17:06:28 +0100 |
From: Ani Sinha <anisinha@redhat.com>
When new dependencies and packages are added to containers, its important to
run CI container generation pipelines on gitlab to make sure that there are no
obvious conflicts between packages that are being added and those that are
already present. Running CI container pipelines will make sure that there are
no such breakages before we commit the change updating the containers. Add a
line in the documentation reminding developers to run the pipeline before
submitting the change. It will also ease the life of the maintainers.
Signed-off-by: Ani Sinha <anisinha@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20230506072012.10350-1-anisinha@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
docs/devel/testing.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
index 203facb417..8f18052ba7 100644
--- a/docs/devel/testing.rst
+++ b/docs/devel/testing.rst
@@ -485,6 +485,12 @@ first to contribute the mapping to the ``libvirt-ci``
project:
`CI <https://www.qemu.org/docs/master/devel/ci.html>`__ documentation
page on how to trigger gitlab CI pipelines on your change.
+ * Please also trigger gitlab container generation pipelines on your change
+ for as many OS distros as practical to make sure that there are no
+ obvious breakages when adding the new pre-requisite. Please see
+ `CI <https://www.qemu.org/docs/master/devel/ci.html>`__ documentation
+ page on how to trigger gitlab CI pipelines on your change.
+
For enterprise distros that default to old, end-of-life versions of the
Python runtime, QEMU uses a separate set of mappings that work with more
recent versions. These can be found in ``tests/lcitool/mappings.yml``.
--
2.39.2
- [PATCH v3 00/36] maintainer omnibus: testing, fuzz, plugins, documentation (pre-PR), Alex Bennée, 2023/06/27
- [PATCH v3 02/36] gitlab: ensure coverage job also publishes meson log, Alex Bennée, 2023/06/27
- [PATCH v3 01/36] gitlab: explicit set artifacts publishing criteria, Alex Bennée, 2023/06/27
- [PATCH v3 04/36] docs/devel: remind developers to run CI container pipeline when updating images,
Alex Bennée <=
- [PATCH v3 06/36] qemu-keymap: properly check return from xkb_keymap_mod_get_index, Alex Bennée, 2023/06/27
- [PATCH v3 10/36] Makefile: add lcitool-refresh to UNCHECKED_GOALS, Alex Bennée, 2023/06/27
- [PATCH v3 11/36] tests/lcitool: update to latest version, Alex Bennée, 2023/06/27
- [PATCH v3 09/36] tests/docker: add test-fuzz, Alex Bennée, 2023/06/27
- [PATCH v3 03/36] gitlab: reduce testing scope of check-gcov, Alex Bennée, 2023/06/27
- [PATCH v3 05/36] tests/tcg: add mechanism to handle plugin arguments, Alex Bennée, 2023/06/27
- [PATCH v3 14/36] tests/lcitool: introduce qemu-minimal, Alex Bennée, 2023/06/27
- [PATCH v3 15/36] tests/docker: convert riscv64-cross to lcitool, Alex Bennée, 2023/06/27
- [PATCH v3 07/36] scripts/oss-fuzz: add a suppression for keymap, Alex Bennée, 2023/06/27
- [PATCH v3 08/36] tests/qtests: clean-up and fix leak in generic_fuzz, Alex Bennée, 2023/06/27