Started by user Lukas Jungmann Running as Lukas Jungmann Agent basic-8m1jb is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: annotations: {} labels: jenkins: "slave" jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd" jenkins/label: "basic" name: "basic-8m1jb" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.jsonp.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "basic-8m1jb" - 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-8m1jb" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.jsonp.svc.cluster.local/jsonp/" image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-4.11.2" 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-jsonp" 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-8m1jb (basic) in workspace /home/jenkins/agent/workspace/publish_tck_pom The recommended git tool is: NONE No credentials specified Cloning the remote Git repository Cloning repository https://github.com/eclipse-ee4j/jsonp.git > git init /home/jenkins/agent/workspace/publish_tck_pom/jsonp-src # timeout=10 Fetching upstream changes from https://github.com/eclipse-ee4j/jsonp.git > git --version # timeout=10 > git --version # 'git version 2.20.1' > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/jsonp.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/eclipse-ee4j/jsonp.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/refs/tags/2.1.0-tck^{commit} # timeout=10 > git rev-parse refs/tags/2.1.0-tck^{commit} # timeout=10 Checking out Revision bb7a2529e72fddb081276c7431e3b1ae5f6bbb2e (refs/tags/2.1.0-tck) > git config core.sparsecheckout # timeout=10 > git checkout -f bb7a2529e72fddb081276c7431e3b1ae5f6bbb2e # timeout=10 Commit message: "Update TCK version of jakarta.json:jakarta.json-tck to 2.1.0" First time build. Skipping changelog. [publish_tck_pom] $ /bin/bash -xe /tmp/jenkins18241341860341945671.sh + TOOLS_PREFIX=/opt/tools + MVN_HOME=/opt/tools/apache-maven/latest + PATH=/opt/tools/apache-maven/latest/bin:/opt/tools/java/openjdk/jdk-11/latest/bin:/opt/tools/java/openjdk/jdk-11/latest/bin:/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + export 'STAGING_PARAMS=-DnexusUrl=https://jakarta.oss.sonatype.org/ -DserverId=ossrh' + STAGING_PARAMS='-DnexusUrl=https://jakarta.oss.sonatype.org/ -DserverId=ossrh' + export STAGING_PLUGIN=org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8 + STAGING_PLUGIN=org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8 + gpg --batch --import **** gpg: directory '/home/jenkins/.gnupg' created gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created gpg: key 005B27E7CA8E530D: public key "Eclipse JSON-P Project " imported gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status gpg: key 005B27E7CA8E530D: secret key imported gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: secret keys imported: 1 ++ gpg --list-keys --with-colons ++ awk -F: '/fpr:/ {print $10}' ++ sort -u + for fpr in $(gpg --list-keys --with-colons | awk -F: '/fpr:/ {print $10}' | sort -u) + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key 2DDF907434310592A49BC0C98F303857EBF3ADD5 trust Secret subkeys are available. pub rsa4096/005B27E7CA8E530D created: 2018-07-27 expires: 2023-07-26 usage: SCEA trust: unknown validity: unknown ssb rsa4096/8F303857EBF3ADD5 created: 2018-07-27 expires: 2023-07-26 usage: S [ unknown] (1). Eclipse JSON-P Project pub rsa4096/005B27E7CA8E530D created: 2018-07-27 expires: 2023-07-26 usage: SCEA trust: unknown validity: unknown ssb rsa4096/8F303857EBF3ADD5 created: 2018-07-27 expires: 2023-07-26 usage: S [ unknown] (1). Eclipse JSON-P Project Please decide how far you trust this user to correctly verify other users' keys (by looking at passports, checking fingerprints from different sources, etc.) 1 = I don't know or won't say 2 = I do NOT trust 3 = I trust marginally 4 = I trust fully 5 = I trust ultimately m = back to the main menu pub rsa4096/005B27E7CA8E530D created: 2018-07-27 expires: 2023-07-26 usage: SCEA trust: ultimate validity: unknown ssb rsa4096/8F303857EBF3ADD5 created: 2018-07-27 expires: 2023-07-26 usage: S [ unknown] (1). Eclipse JSON-P Project Please note that the shown key validity is not necessarily correct unless you restart the program. + for fpr in $(gpg --list-keys --with-colons | awk -F: '/fpr:/ {print $10}' | sort -u) + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key D58760A74BFDE983E890B455005B27E7CA8E530D trust Secret subkeys are available. gpg: checking the trustdb gpg: marginals needed: 3 completes needed: 1 trust model: pgp gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: next trustdb check due at 2023-07-26 pub rsa4096/005B27E7CA8E530D created: 2018-07-27 expires: 2023-07-26 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/8F303857EBF3ADD5 created: 2018-07-27 expires: 2023-07-26 usage: S [ultimate] (1). Eclipse JSON-P Project pub rsa4096/005B27E7CA8E530D created: 2018-07-27 expires: 2023-07-26 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/8F303857EBF3ADD5 created: 2018-07-27 expires: 2023-07-26 usage: S [ultimate] (1). Eclipse JSON-P Project Please decide how far you trust this user to correctly verify other users' keys (by looking at passports, checking fingerprints from different sources, etc.) 1 = I don't know or won't say 2 = I do NOT trust 3 = I trust marginally 4 = I trust fully 5 = I trust ultimately m = back to the main menu pub rsa4096/005B27E7CA8E530D created: 2018-07-27 expires: 2023-07-26 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/8F303857EBF3ADD5 created: 2018-07-27 expires: 2023-07-26 usage: S [ultimate] (1). Eclipse JSON-P Project + cd jsonp-src/tck + mvn -DskipTests clean deploy -pl :jakarta.json-tck -Pstaging [INFO] Scanning for projects... [INFO] [INFO] -------------------< jakarta.json:jakarta.json-tck >-------------------- [INFO] Building Jakarta JSON Processing TCK 2.1.0 [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jakarta.json-tck --- [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ jakarta.json-tck --- [INFO] Installing /home/jenkins/agent/workspace/publish_tck_pom/jsonp-src/tck/pom.xml to /home/jenkins/.m2/repository/jakarta/json/jakarta.json-tck/2.1.0/jakarta.json-tck-2.1.0.pom [INFO] [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ jakarta.json-tck --- [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.044 s [INFO] Finished at: 2022-05-02T12:46:06Z [INFO] ------------------------------------------------------------------------ Finished: SUCCESS