Page MenuHomePhabricator

Upgrade Jenkins to latest LTS 2.375.3
Closed, ResolvedPublic

Description

Jenkins has released a new point release 2.375.3 to their LTS addressing four issues and I have encountered two of them (WMI Windows agent dependency and link to last breadcrumb in the console view). https://www.jenkins.io/changelog-stable/

We are currently running 2.375.2.


Upgrade scheduled for Monday 27th 9:00 UTC


For the upgrades:

releases Jenkins

Then verify the windows-slave.jpi is indeed gone.

contint Jenkins

  • Upgrade the Jenkins package (sudo apt install jenkins)
  • rm /var/lib/jenkins/plugins/windows-slave.jpi or remove it via the Web UI.

I would like to do it on Monday Feb 27th or Tuesday Feb 28th at 9am UTC (10am CET) which is after the MediaWiki backport & config window.

Details

TitleReferenceAuthorSource BranchDest Branch
releasing: remove WMI Windows Agent pluginrepos/releng/jenkins-deploy!17hasharremove-windows-slave-pluginmaster
Customize query in GitLab

Event Timeline

Mentioned in SAL (#wikimedia-operations) [2023-02-20T07:44:06Z] <moritzm> imported jenkins 2.375.3 to thirdparty/ci T330045

From https://debmonitor.wikimedia.org/packages/jenkins :

jenkins_updates.png (262×545 px, 41 KB)

@jnuche and I will proceed with the upgrades at some point this week.

The good news is:

  • Resolve implied dependencies on WMI Windows Agent plugin. (issue 70301)

Which might let us finally get rid of that plugin (windows-slaves).

...
Which might let us finally get rid of that plugin (windows-slaves).

With scap3-dev, I have removed the windows-slave:1.8.1 line from the plugins.txt, removed the jpi and then ran a scap deploy. The plugin still got installed :)

EDIT: I think the deployed repo does not reflect the local state and the plugins.txt still had the windows-slave defined bah.

Upgrade steps moved to task description

releases Jenkins

Upgrade the Jenkins package (sudo apt install jenkins)

Why is that step necessary? It's done automatically by the scap deployment in update_jenkins.sh

scap deploy --environment releasing

Please use the provided script: deploy.sh

Also, let's try to do this on Monday so it doesn't overlap with the train windows.

I have edited the steps in my earlier comment thanks!

We will do the upgrade on Monday Feb 27th at 9:00 UTC / 10:00 CET.

I have send you a calendar invite and added it to the Deployments page.

Checking https://debmonitor.wikimedia.org/packages/jenkins , the two releases Jenkins got upgraded to 2.375.3. I guess due to a scap deployment of jenkins-deploy.

So we only have to do the contint servers.

hashar claimed this task.

Upgraded with @jnuche

jenkins_upgrade.png (268×298 px, 28 KB)