FailedConsole Output

Started by an SCM change
Running as SYSTEM
Agent basic-3dbsp is provisioned from template basic
---
apiVersion: "v1"
kind: "Pod"
metadata:
  annotations: {}
  labels:
    jenkins: "slave"
    jenkins/label: ""
  name: "basic-3dbsp"
spec:
  containers:
  - env:
    - name: "JENKINS_SECRET"
      value: "********"
    - name: "JENKINS_TUNNEL"
      value: "jenkins-discovery.es.svc.cluster.local:50000"
    - name: "JENKINS_AGENT_NAME"
      value: "basic-3dbsp"
    - name: "JENKINS_REMOTING_JAVA_OPTS"
      value: "-showversion -XshowSettings:vm -Xmx256m -Dsun.zip.disableMemoryMapping=true\
        \ -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-3dbsp"
    - name: "JENKINS_AGENT_WORKDIR"
      value: "/home/jenkins/agent"
    - name: "JENKINS_URL"
      value: "http://jenkins-ui.es.svc.cluster.local/es/"
    image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-4.2.1"
    imagePullPolicy: "Always"
    name: "jnlp"
    resources:
      limits:
        memory: "4096Mi"
        cpu: "2000m"
      requests:
        memory: "4096Mi"
        cpu: "1000m"
    securityContext:
      privileged: false
    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
    - mountPath: "/home/jenkins/agent"
      name: "workspace-volume"
      readOnly: false
    workingDir: "/home/jenkins/agent"
  nodeSelector:
    beta.kubernetes.io/os: "linux"
  restartPolicy: "Never"
  securityContext: {}
  volumes:
  - name: "volume-0"
    persistentVolumeClaim:
      claimName: "tools-claim-jiro-es"
      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-3dbsp in workspace /home/jenkins/agent/workspace/security-api-master-build-only
using credential github-bot-ssh
Cloning the remote Git repository
Cloning repository https://github.com/eclipse-ee4j/security-api
 > git init /home/jenkins/agent/workspace/security-api-master-build-only # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/security-api
 > git --version # timeout=10
using GIT_SSH to set credentials GitHub bot SSH
 > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/security-api +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/eclipse-ee4j/security-api # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/eclipse-ee4j/security-api # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/security-api
using GIT_SSH to set credentials GitHub bot SSH
 > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/security-api +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 9dfdbdb30e0088c705d87df56ad78bfc0b1b85e1 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 9dfdbdb30e0088c705d87df56ad78bfc0b1b85e1 # timeout=10
Commit message: "Merge pull request #173 from arjantijms/update_versions"
 > git rev-list --no-walk b40c34bd0e8a3ce79733d72a3ada12a598d81b56 # timeout=10
[security-api-master-build-only] $ /opt/tools/apache-maven/latest/bin/mvn clean install -Pstaging
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/tools/apache-maven/latest
Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: /opt/tools/java/oracle/jdk-8/1.8.0_202/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-1127.el7.x86_64", arch: "amd64", family: "unix"
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] Jakarta Security                                                [bundle]
[INFO] Jakarta Security Parent                                            [pom]
[INFO] Jakarta Security Specification                                     [pom]
[INFO] 
[INFO] ----< jakarta.security.enterprise:jakarta.security.enterprise-api >-----
[INFO] Building Jakarta Security 2.0.0-SNAPSHOT                           [1/3]
[INFO] -------------------------------[ bundle ]-------------------------------
[WARNING] The POM for jakarta.security.auth.message:jakarta.security.auth.message-api:jar:2.0.0 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Jakarta Security Parent 2.0.0-SNAPSHOT:
[INFO] 
[INFO] Jakarta Security ................................... FAILURE [  7.934 s]
[INFO] Jakarta Security Parent ............................ SKIPPED
[INFO] Jakarta Security Specification ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  47.350 s
[INFO] Finished at: 2020-09-02T11:25:34Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jakarta.security.enterprise-api: Could not resolve dependencies for project jakarta.security.enterprise:jakarta.security.enterprise-api:bundle:2.0.0-SNAPSHOT: Could not find artifact jakarta.security.auth.message:jakarta.security.auth.message-api:jar:2.0.0 in sonatype-nexus-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/) -> [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
Build step 'Invoke top-level Maven targets' marked build as failure
Finished: FAILURE