Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Upgrade to latest Jenkins LTS version during CW 3 (January 18-22)


One thing I noticed, other than that the web pages look a little different, is problems that I ultimately tracked down to the version of Java 11.

+ which java
+ java -version
Picked up JAVA_TOOL_OPTIONS: -Xmx2G -DforkCount=1
java version "11" 2018-09-25
Java(TM) SE Runtime Environment 18.9 (build 11+28)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)

Using the above version of Java I quite consistently get many failures like this:

FAILED to load
  ERROR: org.eclipse.oomph.util.IOExceptionWithCause: peer not authenticated: 0 0 0

And like this:

FAILED to load
  ERROR: org.eclipse.oomph.util.IOExceptionWithCause: No PSK available. Unable to resume.: 0 0 0

This started happening after the migration and I finally avoided it by using the version of the installer with an embedded JRE, so I know the problem is caused by the version of Java being used and can make the problem happen again but using that version.

The Java 11 version seems quite old.  Perhaps a newer update would be better.


On 20.01.2021 19:44, Frederic Gurr wrote:

We've completed the upgrade of all our Jenkins instances to the latest
LTS version (2.263.2) a little bit ahead of time.

There is still room for improvement, but this LTS upgrade was quicker
than the last one. This was possible since most of our Jenkins instances
(~220 of 260) are hosted on our cluster based infrastructure and could
be upgraded semi-automatically (so with a lot less clicky-clicky).
=> Kudos to Mikaël Barbero!

Please let us know if anything does not behave the way it should be and
we will take a look.



On 06.01.21 11:58, Frederic Gurr wrote:

We will start the new year with some long overdue Jenkins upgrades.

During CW 3 (January 18-22) we will gradually upgrade all of our CI
instances to the latest Jenkins LTS version to provide new
features and important security updates.

* Why do you spread the upgrade over a week?

We have more than 250 active CI instances that need to be upgraded. To
spread the load and wait for running builds to finish, we distribute the
upgrade over several days.

We are planning to improve this and cut down the required time in the

* How long will my project's CI instance be unavailable?
In most cases, this will require only a restart of each CI instance and
should not take more than an hour (this is a *very* conservative
estimate to be on the safe side). If no builds are running, we simply
run the upgrade. If builds are running, we either wait for them to
complete or contact the projects directly to find a suitable time for a

See also:

NOTE: If you have any important releases planned for this week (CW 21),
please contact us, so we can figure out an alternative time frame.

Please let us know, if you have any other questions or concerns.




Back to the top