[PATCH] docs: Fix example syntax error and update testing.rst

Radosław Śmigielski via Devel posted 1 patch 1 week, 4 days ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/fed6f10ba366a3b23246b50429dabee186e13802.1783087375.git.rsmigiel@redhat.com
docs/testing.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
[PATCH] docs: Fix example syntax error and update testing.rst
Posted by Radosław Śmigielski via Devel 1 week, 4 days ago
From: Radoslaw Smigielski <rsmigiel@redhat.com>

From: Radoslaw Smigielski <rsmigiel@redhat.com>

Fix syntax error in one of the testing examples on alpine-edge image with prefix.

Update CI helper examples to use more recent OS versions:
 - Fedora 38 -> Fedora 44
 - Debian 11 -> Debian 13
 - Debian 10 -> Debian 13

Signed-off-by: Radoslaw Smigielski <rsmigiel@redhat.com>
---
 docs/testing.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/testing.rst b/docs/testing.rst
index 84111ffd4c9e..436e8e8c3910 100644
--- a/docs/testing.rst
+++ b/docs/testing.rst
@@ -137,18 +137,18 @@ the default libvirt registry:
     ...
 
 Now, let's say one would want to run the ``website`` job from GitLab on Debian
-11. This is how a GitLab job specification can be referenced on ``ci/helper``'s
+13. This is how a GitLab job specification can be referenced on ``ci/helper``'s
 command line:
 
 ::
 
-    $ ci/helper run --job website debian-10
+    $ ci/helper run --job website debian-13
 
 What if you want to run an rpmbuild of libvirt on an RPM distro?
 
 ::
 
-    $ ci/helper run --job rpmbuild fedora-38
+    $ ci/helper run --job rpmbuild fedora-44
 
 Want to use your own, say alpine-edge, container image from your GitLab
 container registry?
@@ -156,7 +156,7 @@ Proceed with the following:
 
 ::
 
-    $ ci/helper run --job build --image-prefix registry.gitlab.com/<user>/libvirt/ci- alpine-edge
+    $ ci/helper run --job build --image-prefix registry.gitlab.com/<user>/libvirt/ci-alpine-edge
 
 Finally, it would be nice if one could get an interactive shell inside the
 test environment to debug potential build issues. This can be achieved with the
-- 
2.54.0