![[Jenkins]](/jpa/static/e7ebe0af/images/svgs/logo.svg){kind=logo}
Started by user Lukas Jungmann Running as Lukas Jungmann Agent basic-lhmgj is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: labels: jenkins: "slave" jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd" jenkins/label: "basic" name: "basic-lhmgj" namespace: "jpa" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.jpa.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "basic-lhmgj" - 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-lhmgj" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.jpa.svc.cluster.local/jpa/" image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-3131.vf2b_b_798b_ce99" 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-jpa" 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-lhmgj (basic) in workspace /home/jenkins/agent/workspace/jpa-api-release-finalize [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-Y0hdcUGQNkt4/agent.50 SSH_AGENT_PID=52 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/jpa-api-release-finalize@tmp/private_key_17568670067340099581.key (/home/jenkins/agent/workspace/jpa-api-release-finalize@tmp/private_key_17568670067340099581.key) [ssh-agent] Using credentials jpa-bot (GitHub bot SSH) The recommended git tool is: NONE using credential github-bot-ssh Cloning the remote Git repository Cloning repository git@github.com:jakartaee/persistence.git > git init /home/jenkins/agent/workspace/jpa-api-release-finalize # timeout=10 Fetching upstream changes from git@github.com:jakartaee/persistence.git > git --version # timeout=10 > git --version # 'git version 2.20.1' using GIT_SSH to set credentials GitHub bot SSH [INFO] Currently running in a labeled security context > /usr/bin/chcon --type=ssh_home_t /home/jenkins/agent/workspace/jpa-api-release-finalize@tmp/jenkins-gitclient-ssh10350372811368504572.key Verifying host key using manually-configured host key entries > git fetch --tags --force --progress -- git@github.com:jakartaee/persistence.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url git@github.com:jakartaee/persistence.git # 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 247904a61fc54f87422fd5df7bf41b1f0e6c84e7 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 247904a61fc54f87422fd5df7bf41b1f0e6c84e7 # timeout=10 Commit message: "update GH build to use SE 21" First time build. Skipping changelog. [jpa-api-release-finalize] $ /bin/bash -e /tmp/jenkins3918733890975411150.sh -[ Reading project identifiers ]------------------------------------------------ Action: list Repository ID prefix: jakartapersistence -[ JAXB API Staging Repository List ]------------------------------------------- WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.thoughtworks.xstream.core.util.Fields (file:/home/jenkins/.m2/repository/com/thoughtworks/xstream/xstream/1.4.7/xstream-1.4.7.jar) to field java.util.TreeMap.comparator WARNING: Please consider reporting this to the maintainers of com.thoughtworks.xstream.core.util.Fields WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] jakartapersistence-1000 CLOSED jakarta.persistence:jakarta.persistence-spec:2.2 [INFO] jakartapersistence-1004 CLOSED jakarta.persistence:jakarta.persistence-spec:3.0 [INFO] jakartapersistence-1006 CLOSED jakarta.persistence:persistence-spec:3.0 [INFO] jakartapersistence-1014 CLOSED jakarta.persistence:persistence-spec:3.1 [INFO] jakartapersistence-1016 CLOSED jakarta.persistence:persistence-spec:3.2-DRAFT01 [INFO] jakartapersistence-1017 CLOSED jakarta.persistence:jakarta.persistence-api:3.2.0-B01 $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 52 killed; [ssh-agent] Stopped. Finished: SUCCESS