Pinal Shah created ATLAS-4946:
---------------------------------
Summary: Atlas-master-snapshot-publish jenkins job is failing
constantly
Key: ATLAS-4946
URL: https://issues.apache.org/jira/browse/ATLAS-4946
Project: Atlas
Issue Type: Task
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
Below is the analysis
* For the this issue, it is picking jdk17 to run, even though it is configured
for jdk11.
{quote}[Atlas-master-snapshot-publish] $
/usr/local/asfpackages/java/adoptium-jdk-17.0.7+7/bin/java -Xmx16g -Xms16g
-Dfile.encoding=UTF-8 -Dproject.build.sourceEncoding=UTF-8 -cp
/home/jenkins/maven35-agent.jar:/home/jenkins/tools/maven/apache-maven-3.6.3/boot/plexus-classworlds-2.6.0.jar:/home/jenkins/tools/maven/apache-maven-3.6.3/conf/logging
jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/apache-maven-3.6.3
/home/jenkins/agent.jar /home/jenkins/maven35-interceptor.jar
/home/jenkins/maven3-interceptor-commons.jar{quote}
* Because of below error
{quote}Caused by: java.lang.UnsupportedClassVersionError:
jenkins/security/MasterToSlaveCallable has been compiled by a more recent
version of the Java Runtime (class file version 61.0), this version of the Java
Runtime only recognizes class file versions up to 55.0{quote}
* Current version of Cloudbees CI is 2.479.2.3 which was released on 27th
November. After 2.479.1.3 version Java11 is no longer supported.
* I think this might be the reason. but the last stable build was on 28th
November.
* PreCommit-ATLAS-Build-Test is running, because it is still picking java8.
* Below things i tried to configure for Atlas-master-snapshot-publish but
didn't work
- Tried setting jdk8
- Tried exporting JAVA_HOME
* With jdk17 it was failing with maven-war-plugin because of ATLAS-4942
* After resolving above it fails with enunciate-maven-plugin
* Currently Atlas uses 2.13.2 which is not compatible with jdk17, the latest
available version is 2.18.1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
