Re: Switching default build node to centos8-builder-4c-4g

Robert Varga

On 22/04/2022 10:11, Anil Belur wrote:
+1 We should be able switch to CentOS8 for the jobs that require JDK17, but there could be a few caveats that we should consider before we move the rest of the builders nodes.
Sigul (artifact signing) is built on CentOS7 and may not be compatible when we try to sign artifact on CentOS8.
Hmm, that would be a major problem and really soon. Sigul is part of stage jobs -- stage i.e. build + sign. We are exactly 2 patches away from odlparent/master requiring JDK17 to build -- and that just does not work on CentOS7.

We need either Sigul+CentOS8 or JDK17+CentOS7. The former is obviously the preferred solution.

Or, we need decoupling of stage's build and sign steps in a reliable manner -- which would really call for Jenkins Pipelines, but we have not even dipped our toes in that particular ocean...


On Thu, Apr 21, 2022 at 9:14 AM Robert Varga <nite@... <mailto:nite@...>> wrote:
Hello everyone,
we are currently defaulting to centos7-builder-4c-4g here:
CentOS7 is ancient and cannot support our releases going forward, as it
lacks JDK17 -- which is scheduled to be required for Chlorine.
MRI projects have already switched to CentOS (Stream) 8, like here:
That having been said and provided we get a fix for
I propose we switch the default build node to CentOS 8 and deal with
whatever fallout -- probably in June, as that is essentially quiet with
only Chlorine prep on the table.
Whaddya say?

Join { to automatically receive all group messages.