From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Tianrui Zhao" <zhaotianrui@loongson.cn>,
"Song Gao" <gaosong@loongson.cn>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Xianglai Li" <lixianglai@loongson.cn>,
"Zhiguo Wu" <wuzhiguo@loongson.cn>,
"Erik Skultety" <eskultet@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: [RFC PATCH 0/9] scripts/ci: Consolidate Ansible playbook rules
Date: Thu, 4 Jan 2024 17:07:56 +0100 [thread overview]
Message-ID: <20240104160805.56856-1-philmd@linaro.org> (raw)
Hi,
The CI Ansible playbook scripts failed when trying to provision
a openEuler instance. I was going to do a manual installation,
but Alex strongly suggested to keep using Ansible, implicitly
asking to fix the scripts :) This is what this series does.
Note, when libvirt-ci is upgraded, we neglect to update the
playbook packages list. Not sure how to automate that, so I
updated manually.
Philippe Mathieu-Daudé (9):
scripts/ci: Do not enforce gitlab-runner path
scripts/ci: Do not restrict spice package to x86/arm hosts
scripts/ci: Split EL8 specific packages out of Centos8 list
scripts/ci: Update Centos8 package list
scripts/ci: Restrict libpmem-devel package to x86 hosts
scripts/ci: Install libxdp-devel on x86 hosts
scripts/ci: Install RH packages on RH derivative distros
scripts/ci: Update Ubuntu packages list
scripts/ci: Restrict libpmem-dev and libxen-dev packages to x86 hosts
scripts/ci/setup/build-environment.yml | 123 +++++++++++++++++++++----
scripts/ci/setup/gitlab-runner.yml | 6 +-
2 files changed, 107 insertions(+), 22 deletions(-)
--
2.41.0
next reply other threads:[~2024-01-04 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 16:07 Philippe Mathieu-Daudé [this message]
2024-01-04 16:07 ` [PATCH 1/9] scripts/ci: Do not enforce gitlab-runner path Philippe Mathieu-Daudé
2024-01-04 16:07 ` [PATCH 2/9] scripts/ci: Do not restrict spice package to x86/arm hosts Philippe Mathieu-Daudé
2024-01-04 16:07 ` [RFC PATCH 3/9] scripts/ci: Split EL8 specific packages out of Centos8 list Philippe Mathieu-Daudé
2024-01-04 16:08 ` [RFC PATCH 4/9] scripts/ci: Update Centos8 package list Philippe Mathieu-Daudé
2024-01-04 16:08 ` [RFC PATCH 5/9] scripts/ci: Restrict libpmem-devel package to x86 hosts Philippe Mathieu-Daudé
2024-01-04 16:08 ` [RFC PATCH 6/9] scripts/ci: Install libxdp-devel on " Philippe Mathieu-Daudé
2024-01-04 16:08 ` [RFC PATCH 7/9] scripts/ci: Install RH packages on RH derivative distros Philippe Mathieu-Daudé
2024-01-04 16:08 ` [RFC PATCH 8/9] scripts/ci: Update Ubuntu packages list Philippe Mathieu-Daudé
2024-01-04 16:08 ` [RFC PATCH 9/9] scripts/ci: Restrict libpmem-dev and libxen-dev packages to x86 hosts Philippe Mathieu-Daudé
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=20240104160805.56856-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=eskultet@redhat.com \
--cc=gaosong@loongson.cn \
--cc=lixianglai@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wuzhiguo@loongson.cn \
--cc=yangxiaojuan@loongson.cn \
--cc=zhaotianrui@loongson.cn \
/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).