Hey,
Thanks for the heads up (and apologies for the delay). I finally upgraded our (systemd) Jenkins and it's now sitting on 2.440.3. Although, it now complains about:
You are running Jenkins on Java 11, support for which will end on or after Sep 30, 2024. Refer to the documentation for more details.
I guess you can never win ;)
Also, while redeploying the Jenkins pod it somehow managed to nuke the entire clouds section, but thankfully I had a backup of our config.xml at hand. After copying the missing section back into the live configuration (and restarting Jenkins) everything seems to be in order.
On 6/6/24 17:19, Fabian Arrotin wrote:
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/4...)
- 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 exitWatch 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
CI-users mailing list -- ci-users@lists.centos.org To unsubscribe send an email to ci-users-leave@lists.centos.org