On Thu, Apr 25, 2024 at 05:03:43PM +0200, Thomas Huth wrote:
> On 12/04/2024 12.37, Paolo Bonzini wrote:
> > RHEL 9 (and thus also the derivatives) are available since two years
> > now, so according to QEMU's support policy, we can drop the active
> > support for the previous major version 8 now.
> >
> > Thus upgrade our CentOS Stream build environment playbooks to major
> > version 9 now.
> >
> > Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
> > ---
> > .../stream/{8 => 9}/build-environment.yml | 31 ++++++-------
> > .../stream/{8 => 9}/x86_64/configure | 4 +-
> > .../stream/{8 => 9}/x86_64/test-avocado | 0
> > scripts/ci/setup/build-environment.yml | 44 +++++++------------
> > 4 files changed, 34 insertions(+), 45 deletions(-)
> > rename scripts/ci/org.centos/stream/{8 => 9}/build-environment.yml (75%)
> > rename scripts/ci/org.centos/stream/{8 => 9}/x86_64/configure (98%)
> > rename scripts/ci/org.centos/stream/{8 => 9}/x86_64/test-avocado (100%)
>
> Hi Paolo!
>
> Not sure whether you've seen my busted pull request, but anyway: It seems
> like this was not enough to update the custom runner. You also need to
> update .gitlab-ci.d/custom-runners/centos-stream-8-x86_64.yml for this.
>
> By the way, who has access to the s390x custom runner and could update it to
> Ubuntu 22.04 now? It still seems to work with 20.04 which will be out of
> support from the QEMU POV next week...
I rather wish that the custom runners were all using podman/docker,
so we could have the jobs just build containers for the envs, like
we do on shared runners, and/or on the Azure runners. That way we're
not beholden to an admin to manually update OS intsalls.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
