Hi all,
We seem to have issue with an IBM Power 8 used within CI and so we have
to re-balance CI nodes that you can request through Duffy API for
ppc64/ppc64le.
My question sounds more like a survey : I think that most (if not all)
CI projects actually still building (and testing in CI) just target the
ppc64le architecture (Little Endian) and so not the ppc64 (Big Endian) one.
We'd like to hear from you and depending on the needs, we can
eventually drop ppc64 architecture for CI tests, and so have more
(re-balanced) ppc64le resources .
Opinions ?
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab
Hi folks,
We are planning to update all the plugins (compatible) installed on
ci.centos.org jenkins instance.
I will do it tomorrow morning (Dec 18th) at 9am UTC. I will start
preparing for shutdown then and all the jobs triggered post that will
go in the queue until the instance has updated the plugin and
restarted.
I would also like to open a question to you all who are using OCP4
cluster. How would you want to manage Jenkins update for your
namespace? There are multiple ways from them being auto updated
whenever we update the cluster (this is by default that we use),
time'd/self trigger updates, or updates on change in tags.
I am interested in hearing your thoughts.
Thank you
--
Vipul Siddharth
He/His/Him
Fedora | CentOS CI Infrastructure Team