Console Output

Push event to branch 3.1
04:29:17 Connecting to https://api.github.com using GitHub bot (username/token)
Obtained etc/jenkins/Jenkinsfile_ci_build from 9a88261454f44fe09348efeee8a9f9827516c96a
[Pipeline] Start of Pipeline
[Pipeline] timeout
Timeout set to expire after 1 day 6 hr without activity
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Jersey build)
[Pipeline] parallel
[Pipeline] { (Branch: JDK 11)
[Pipeline] { (Branch: JDK 21)
[Pipeline] stage
[Pipeline] { (JDK 11)
[Pipeline] stage
[Pipeline] { (JDK 21)
[Pipeline] node
[Pipeline] node
Agent centos-7-h5qvb is provisioned from template centos-7
---
apiVersion: "v1"
kind: "Pod"
metadata:
  labels:
    jenkins: "slave"
    jenkins/label-digest: "55a177a28a71a1957f582df488f25d8c2f70df30"
    jenkins/label: "migration_jipp-migration_centos-7"
  name: "centos-7-h5qvb"
  namespace: "jersey"
spec:
  containers:
  - env:
    - name: "JENKINS_SECRET"
      value: "********"
    - name: "JENKINS_TUNNEL"
      value: "jenkins-discovery.jersey.svc.cluster.local:50000"
    - name: "JENKINS_AGENT_NAME"
      value: "centos-7-h5qvb"
    - 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: "centos-7-h5qvb"
    - name: "JENKINS_AGENT_WORKDIR"
      value: "/home/jenkins/agent"
    - name: "JENKINS_URL"
      value: "http://jenkins-ui.jersey.svc.cluster.local/jersey/"
    image: "docker.io/eclipsecbi/jiro-agent-centos-7: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-jersey"
      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"

Running on centos-7-h5qvb in /home/jenkins/agent/workspace/ci-cd-integration_3.1
[Pipeline] {
[Pipeline] checkout
The recommended git tool is: git
Creating placeholder flownodes because failed loading originals.
ERROR: Cannot resume build because FlowNode 18 for FlowHead 1 could not be loaded. This is expected to happen when using the PERFORMANCE_OPTIMIZED durability setting and Jenkins is not shut down cleanly. Consider investigating to understand if Jenkins was not shut down cleanly or switching to the MAX_SURVIVABILITY durability setting which should prevent this issue in most cases.

GitHub has been notified of this commit’s build result

Finished: FAILURE