Started by upstream project "pages-master" build number 90 originally caused by: Started by an SCM change Running as SYSTEM Agent basic-zd030 is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: labels: jenkins: "slave" jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd" jenkins/label: "basic" name: "basic-zd030" 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-zd030" - 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-zd030" - 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-zd030 (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 31096e234cc8d2db6e66c2505166683cf2a6deea (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 31096e234cc8d2db6e66c2505166683cf2a6deea # timeout=10 Commit message: "Update EL API to 6.0.0-RC1" > git rev-list --no-walk ab6702360f0a4ae77ef9005640e2b70f24bf8743 # timeout=10 [jsp-api-copyright-check-master] $ /bin/bash -e /tmp/jenkins14512331800963837443.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 ]--------------------------------- [WARNING] The POM for jakarta.servlet:jakarta.servlet-api:jar:6.1.0-SNAPSHOT is missing, no dependency information available [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.254 s [INFO] Finished at: 2024-02-27T10:52:44Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project jakarta.servlet.jsp-api: Could not resolve dependencies for project jakarta.servlet.jsp:jakarta.servlet.jsp-api:jar:4.0.0-SNAPSHOT: The following artifacts could not be resolved: jakarta.servlet:jakarta.servlet-api:jar:6.1.0-SNAPSHOT (absent): Could not find artifact jakarta.servlet:jakarta.servlet-api:jar:6.1.0-SNAPSHOT -> [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/DependencyResolutionException Finished: SUCCESS