Releng JIPP fails builds due to using Java 8
As can be seen at https://ci.eclipse.org/releng/job/I-build-4.25/116/console build fails with:
java.lang.UnsupportedClassVersionError: com/trilead/ssh2/ServerHostKeyVerifier has been compiled by a more recent
version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file
versions up to 52.0
but Java 11 has been the default one since yesterday.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
This seem to be caused by the Jenkins update today we saw here: https://github.com/eclipse-pde/eclipse.pde/pull/266#issuecomment-1203727854
- Frederic Gurr added IT-prioritymedium IT-severitynormal ~24521 statetodo team:releng labels
added IT-prioritymedium IT-severitynormal ~24521 statetodo team:releng labels
- Reporter
I'll take a look.
- Frederic Gurr changed the description
Compare with previous version changed the description
- Reporter
AFAICT, the default JDK version of the docker image must be set to JDK11. For the centos8 image, it's currently set to JDK8.
I was not able to set the JDK early enough by either modifying the PATH environment variable or in the
tools
section.While debugging that, I also found some oddities in the
I-build.groovy
script:- container name was set to
jnlp
- container command was not set
- container name was set to
Can we revert Jenkins update until we have right docker build? Everything was OK before update.
How one can set default docker JDK for centos image?
- Reporter
Can we revert Jenkins update until we have right docker build? Everything was OK before update.
Creating the right docker image is easier than reverting the Jenkins update. I'm on it.
How one can set default docker JDK for centos image?
In the dockerfile:
RUN alternatives --set java /usr/lib/jvm/java-11-openjdk/bin/java
1 - Author
Any progress on this one? Should we switch to our own container?
Edited by Aleksandar Kurtakov Collapse replies - Reporter
We have a solution, but we are still wrangling with a docker build.
- Author
Weirdly enough only Cent8 is broken. In another failing job I switched to Cent7 https://ci.eclipse.org/releng/job/deploy-eclipse-platform-parent-pom/jobConfigHistory/showDiffFiles?timestamp1=2022-08-04_01-04-54×tamp2=2022-08-04_01-06-23 and build worked.
- Reporter
On CentOS 7, JDK11 is already set as the default JDK.
- Author
I even wonder whether it's not time to set default JVM to Java 17 nowadays. To prevent same pain in few months.
- Reporter
We will align the JDK version to requirements in Jenkins.
- Reporter
I have opened a PR to change the docker image to CentOS 8 with JDK11:
https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/pull/437
Thanks, SDK build went through now. We can close this ticket.
1- Frederic Gurr assigned to @fgurr
assigned to @fgurr
- Frederic Gurr closed
closed
- Frederic Gurr removed statetodo label
removed statetodo label
- Frederic Gurr mentioned in issue #1636 (closed)
mentioned in issue #1636 (closed)
- Reporter
Not sure why build #126 through #128 used the
centos-8
instead of thecentos-8-jdk11
image, but the problem seems to be gone since build #129. Please re-open if it happens again. - Frederic Gurr mentioned in commit heurtemattes/jiro-agents@ec700307
mentioned in commit heurtemattes/jiro-agents@ec700307