Started by upstream project "pages-master" build number 98
originally caused by:
Started by an SCM change
Running as SYSTEM
Agent basic-v05sq is provisioned from template basic
---
apiVersion: "v1"
kind: "Pod"
metadata:
labels:
jenkins: "slave"
jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd"
jenkins/label: "basic"
name: "basic-v05sq"
namespace: "jsp"
spec:
containers:
- env:
- name: "JENKINS_SECRET"
value: "********"
- name: "JENKINS_TUNNEL"
value: "jenkins-discovery.jsp.svc.cluster.local:50000"
- name: "JENKINS_AGENT_NAME"
value: "basic-v05sq"
- name: "JENKINS_REMOTING_JAVA_OPTS"
value: "-showversion -XshowSettings:vm -Xmx256m -Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=true\
\ -Dorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true"
- name: "JAVA_TOOL_OPTIONS"
value: ""
- name: "_JAVA_OPTIONS"
value: ""
- name: "OPENJ9_JAVA_OPTIONS"
value: "-XX:+IgnoreUnrecognizedVMOptions -XX:+IdleTuningCompactOnIdle -XX:+IdleTuningGcOnIdle"
- name: "JENKINS_NAME"
value: "basic-v05sq"
- name: "JENKINS_AGENT_WORKDIR"
value: "/home/jenkins/agent"
- name: "JENKINS_URL"
value: "http://jenkins-ui.jsp.svc.cluster.local/jsp/"
image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-3160.vd76b_9ddd10cc"
imagePullPolicy: "Always"
name: "jnlp"
resources:
limits:
cpu: "2000m"
memory: "4096Mi"
requests:
cpu: "1000m"
memory: "4096Mi"
tty: true
volumeMounts:
- mountPath: "/home/jenkins/.m2/toolchains.xml"
name: "m2-dir"
readOnly: true
subPath: "toolchains.xml"
- mountPath: "/home/jenkins/.mavenrc"
name: "m2-dir"
readOnly: true
subPath: ".mavenrc"
- mountPath: "/opt/tools"
name: "volume-0"
readOnly: false
- mountPath: "/home/jenkins"
name: "volume-2"
readOnly: false
- mountPath: "/home/jenkins/.m2/repository"
name: "volume-3"
readOnly: false
- mountPath: "/home/jenkins/.m2/settings-security.xml"
name: "m2-secret-dir"
readOnly: true
subPath: "settings-security.xml"
- mountPath: "/home/jenkins/.m2/wrapper"
name: "volume-4"
readOnly: false
- mountPath: "/home/jenkins/.m2/settings.xml"
name: "m2-secret-dir"
readOnly: true
subPath: "settings.xml"
- mountPath: "/home/jenkins/.ssh"
name: "volume-1"
readOnly: false
subPath: ""
- mountPath: "/home/jenkins/agent"
name: "workspace-volume"
readOnly: false
workingDir: "/home/jenkins/agent"
nodeSelector:
kubernetes.io/os: "linux"
restartPolicy: "Never"
volumes:
- name: "volume-0"
persistentVolumeClaim:
claimName: "tools-claim-jiro-jsp"
readOnly: true
- name: "m2-secret-dir"
secret:
secretName: "m2-secret-dir"
- emptyDir:
medium: ""
name: "volume-2"
- configMap:
name: "m2-dir"
name: "m2-dir"
- configMap:
name: "known-hosts"
name: "volume-1"
- emptyDir:
medium: ""
name: "workspace-volume"
- emptyDir:
medium: ""
name: "volume-4"
- emptyDir:
medium: ""
name: "volume-3"
Building remotely on basic-v05sq (basic) in workspace /home/jenkins/agent/workspace/jsp-api-copyright-check-master
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/eclipse-ee4j/jsp-api
> git init /home/jenkins/agent/workspace/jsp-api-copyright-check-master # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/jsp-api
> git --version # timeout=10
> git --version # 'git version 2.20.1'
> git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/jsp-api +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/eclipse-ee4j/jsp-api # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 65e89c3074ef6f72ae1810506b90ffb8a9a480c3 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 65e89c3074ef6f72ae1810506b90ffb8a9a480c3 # timeout=10
Commit message: "Add dependency required to run the tests"
> git rev-list --no-walk 3956175598329168104fb8629b69fa1da3c2eae4 # timeout=10
[jsp-api-copyright-check-master] $ /bin/bash -e /tmp/jenkins9180082691657861822.sh
[INFO] Scanning for projects...
[INFO]
[INFO] ------------< jakarta.servlet.jsp:jakarta.servlet.jsp-api >-------------
[INFO] Building Jakarta Server Pages API 4.0.0-SNAPSHOT
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ jakarta.servlet.jsp-api ---
[INFO]
[INFO] --- glassfish-copyright:2.4:copyright (default-cli) @ jakarta.servlet.jsp-api ---
[INFO]
[INFO] --- enforcer:3.4.1:enforce (enforce-maven) @ jakarta.servlet.jsp-api ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion passed
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ jakarta.servlet.jsp-api ---
[INFO] Copying 1 resource from src/main/java to target/classes
[INFO] Copying 2 resources from .. to target/classes/META-INF
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ jakarta.servlet.jsp-api ---
[WARNING] Can't extract module name from jakarta.el-api-6.0.0.jar: Unsupported major.minor version 61.0
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 43 source files with javac [debug release 17 module-path] to target/classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.517 s
[INFO] Finished at: 2024-05-08T17:08:18Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) on project jakarta.servlet.jsp-api: Fatal error compiling: error: release version 17 not supported -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Finished: SUCCESS