CI-users June 2024

ci-users@lists.centos.org

3 participants
3 discussions

Reminder : CentOS 7 and 8s EOL soon (impact on CI workflow)
by Fabian Arrotin 27 Jun '24

27 Jun '24

Hi CI tenants ! Just a reminder that (as you know it) CentOS Stream 8 will go EOL in May and then CentOS Linux 7 itself going EOL in June (so very soon) That would mean that we'll just remove the various pools that provide CentOS 8s and 7 for your tests. Reason is that mirror network itself will be unavailable and so all tests would fail anyway. Happy to discuss here but we'll send reminders about when we'll just remove the various pools in Duffy. I also need to find an option for something else that you *still* all use when using Jenkins on openshift cluster : our cico-workspace image (https://quay.io/repository/centosci/cico-workspace) That one is "problematic" as it's based on upstream openshift jenkins agent (https://github.com/openshift/jenkins/tree/master?tab=readme-ov-file#hosted-…) These ones are based on UBI8 and it seems that there is (still) no momentum to move to UBI9 (don't have direct contact with them though) While our current images were based from the upstream ones, we could just "convert" these to 8s (https://github.com/centosci/images/blob/master/cico-workspace/Dockerfile#L1 and https://github.com/centosci/images/blob/master/cico-workspace/Dockerfile#L8) We need to find a solution but was wondering if just using vault (archived mirror content) would be a good solution or not : tempted myself to answer "no" as that would mean running container that will *never* be updated for security reasons (CentOS Stream 8 going EOL in May) Opinions, thoughts ? -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

3 6

[action required] Updating Jenkins pods for CI tenants (openshift)
by Fabian Arrotin 19 Jun '24

19 Jun '24

Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version) Long story short (people can read https://pagure.io/centos-infra/issue/1409) : - Openshift (during releases) modified the default jenkins imagestreamtag (https://access.redhat.com/documentation/en-us/openshift_container_platform/…) - deployed jenkins pods were using DeploymentConfig using jenkins:2 imagestreamtag (not up2date) What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) : ``` oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade-redeploy" and exit ``` Watch for your logs and then update your plugins Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

3 6

CentOS Stream 8 nodes removed from Duffy/CI pools
by Fabian Arrotin 03 Jun '24

03 Jun '24

As announced some time ago, CentOS Stream 8 reached EOL (End Of Life) and so will be archived today. For that reason, CentOS Stream 8 duffy nodes (see https://sigs.centos.org/guide/ci/#duffy-ephemeral-bare-metalvirtual-machine…) were removed from configuration and pool cleared out Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CI-users June 2024