|
From: | Philippe Mathieu-Daudé |
Subject: | Re: [PATCH 07/12] testing: update ubuntu2004 to ubuntu2204 |
Date: | Wed, 22 Feb 2023 16:11:45 +0100 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 |
On 17/2/23 18:14, Daniel P. Berrangé wrote:
On Fri, Feb 17, 2023 at 11:35:44AM -0500, John Snow wrote:
However, would it be possible to keep the older Ubuntu test as a manual execution that we could invoke at will, only during RC testing phase? If it's not a lot of work, I could even check that in myself as a follow-up if it isn't unwanted. I find that "oldest version of x" is quite useful to me for testing Python stuff in particular, as that ecosystem moves pretty fast. It'd be mighty convenient to me in particular to keep an old Ubuntu test around to run manually as needed. (Heck, even if it wasn't on CI at all but was just a container I could run locally, that would still be quite useful.) Whaddaya think?It would be pretty trivial to have tests/docker/dockerfiles contain Dockerfiles for *every* supported distro version we have, and then only build & test a subset in CI. It would merely suggest that we
That would be great! Could be added as byte-sized issue.
change our naming convention so the dockerfiles in that dir include the version. Basically adopting the standard libvirt-ci naming convention for targets of $OSNAME-$OSVERSION: $ lcitool targets almalinux-8 almalinux-9 alpine-315 alpine-316 alpine-edge centos-stream-8 centos-stream-9 debian-10 debian-11 debian-sid fedora-36 fedora-37 fedora-rawhide freebsd-12 freebsd-13 freebsd-current macos-12 macos-13 opensuse-leap-153 opensuse-leap-154 opensuse-tumbleweed ubuntu-1804 ubuntu-2004 ubuntu-2204 Contributors can then use 'make docker-XXXX' to run build tests locally on specific distros when they need to test something that isn't covered by default in out gating CI With regards, Daniel
[Prev in Thread] | Current Thread | [Next in Thread] |