NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2026-09-03 20:53:04 -05:00
Code Issues Packages Projects Releases Wiki Activity

docs: Fix example syntax error and update testing.rst

Browse Source 
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>
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
This commit is contained in:
Radoslaw Smigielski
2026-07-16 16:17:24 +02:00
committed by Peter Krempa
parent 212580e6b3
commit 7bc888dddd
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/testing.rst
+4 -4
View File
@@ -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