From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH] ci: move external build environment setups to CentOS Stream 9
Date: Thu, 25 Apr 2024 16:44:29 +0100 [thread overview]
Message-ID: <Zip6XaU70q6k0uut@redhat.com> (raw)
In-Reply-To: <73911b7b-da94-441a-95b0-bcfb23f7b8fb@redhat.com>
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 <pbonzini@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 :|
prev parent reply other threads:[~2024-04-25 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 10:37 [PATCH] ci: move external build environment setups to CentOS Stream 9 Paolo Bonzini
2024-04-12 10:50 ` Thomas Huth
2024-04-25 15:03 ` Thomas Huth
2024-04-25 15:44 ` Daniel P. Berrangé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zip6XaU70q6k0uut@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).