Started by user arjan tijms Running as arjan tijms Agent basic-vvck5 is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: labels: jenkins: "slave" jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd" jenkins/label: "basic" name: "basic-vvck5" namespace: "authorization" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.authorization.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "basic-vvck5" - 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-vvck5" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.authorization.svc.cluster.local/authorization/" 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-authorization" 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-vvck5 (basic) in workspace /home/jenkins/agent/workspace/3_authorization-api-staging-to-release [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-qWc5DzlgpiMP/agent.54 SSH_AGENT_PID=56 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/3_authorization-api-staging-to-release@tmp/private_key_7525584889570464832.key (/home/jenkins/agent/workspace/3_authorization-api-staging-to-release@tmp/private_key_7525584889570464832.key) [ssh-agent] Using credentials eclipse-authorization-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/authorization.git > git init /home/jenkins/agent/workspace/3_authorization-api-staging-to-release # timeout=10 Fetching upstream changes from git@github.com:jakartaee/authorization.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/3_authorization-api-staging-to-release@tmp/jenkins-gitclient-ssh7438262559551695370.key Verifying host key using manually-configured host key entries > git fetch --tags --force --progress -- git@github.com:jakartaee/authorization.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url git@github.com:jakartaee/authorization.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 328fbee805c4c7497a3087f71a6718355d524c99 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 328fbee805c4c7497a3087f71a6718355d524c99 # timeout=10 Commit message: "Merge pull request #139 from arjantijms/tidy_m1" First time build. Skipping changelog. [3_authorization-api-staging-to-release] $ /bin/sh -xe /tmp/jenkins7562535689493198208.sh + gpg --batch --import **** gpg: directory '/home/jenkins/.gnupg' created gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created gpg: key 57A170137B7D6C03: 1 signature not checked due to a missing key gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created gpg: key 57A170137B7D6C03: public key "Eclipse Project for JACC <jacc-dev@eclipse.org>" imported gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status gpg: key 57A170137B7D6C03: secret key imported gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: secret keys imported: 1 gpg: no ultimately trusted keys found ++ 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 4DBCFD83F814F5BCA1F7128157A170137B7D6C03 trust Secret subkeys are available. pub rsa4096/57A170137B7D6C03 created: 2018-09-29 expires: 2028-10-02 usage: SCEA trust: unknown validity: unknown ssb rsa4096/686823BE17A98D9D created: 2018-09-29 expires: 2028-10-02 usage: S [ unknown] (1). Eclipse Project for JACC <jacc-dev@eclipse.org> pub rsa4096/57A170137B7D6C03 created: 2018-09-29 expires: 2028-10-02 usage: SCEA trust: unknown validity: unknown ssb rsa4096/686823BE17A98D9D created: 2018-09-29 expires: 2028-10-02 usage: S [ unknown] (1). Eclipse Project for JACC <jacc-dev@eclipse.org> 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/57A170137B7D6C03 created: 2018-09-29 expires: 2028-10-02 usage: SCEA trust: ultimate validity: unknown ssb rsa4096/686823BE17A98D9D created: 2018-09-29 expires: 2028-10-02 usage: S [ unknown] (1). Eclipse Project for JACC <jacc-dev@eclipse.org> 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 72152A32DFFAC5E16D52609F686823BE17A98D9D 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 2028-10-02 pub rsa4096/57A170137B7D6C03 created: 2018-09-29 expires: 2028-10-02 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/686823BE17A98D9D created: 2018-09-29 expires: 2028-10-02 usage: S [ultimate] (1). Eclipse Project for JACC <jacc-dev@eclipse.org> pub rsa4096/57A170137B7D6C03 created: 2018-09-29 expires: 2028-10-02 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/686823BE17A98D9D created: 2018-09-29 expires: 2028-10-02 usage: S [ultimate] (1). Eclipse Project for JACC <jacc-dev@eclipse.org> 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/57A170137B7D6C03 created: 2018-09-29 expires: 2028-10-02 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/686823BE17A98D9D created: 2018-09-29 expires: 2028-10-02 usage: S [ultimate] (1). Eclipse Project for JACC <jacc-dev@eclipse.org> [3_authorization-api-staging-to-release] $ /bin/sh -ex /tmp/jenkins11868284696279026881.sh + TOOLS_PREFIX=/opt/tools + JAVA_PREFIX=/opt/tools/java/oracle + MVN_HOME=/opt/tools/apache-maven/latest + JAVA_HOME=/opt/tools/java/oracle/jdk-8/latest + PATH=/opt/tools/apache-maven/latest/bin:/opt/tools/java/oracle/jdk-8/latest/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + MVN_EXTRA='--batch-mode -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn' + BUILD_DIR=/home/jenkins/agent/workspace/3_authorization-api-staging-to-release + cd /home/jenkins/agent/workspace/3_authorization-api-staging-to-release + echo '-[ Release to Maven Central ]-------------------------------------' -[ Release to Maven Central ]------------------------------------- + mvn --batch-mode -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn nexus-staging:rc-release -DserverId=ossrh -DnexusUrl=https://jakarta.oss.sonatype.org/ -DstagingRepositoryId=jakartaauthorization-1007 '-DstagingDescription=Release to Maven Central' [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Jakarta Authorization [jar] [INFO] Jakarta Authorization Specification [pom] [INFO] Jakarta Authorization Parent [pom] [INFO] [INFO] --------< org.eclipse.ee4j.authorization:authorization-parent >--------- [INFO] Building Jakarta Authorization Parent 3.0.0-SNAPSHOT [1/3] [INFO] from pom.xml [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- nexus-staging:1.6.13:rc-release (default-cli) @ authorization-parent --- [INFO] + Using server credentials "ossrh" from Maven settings. [INFO] * Connected to Nexus at https://jakarta.oss.sonatype.org:443/, is version 2.15.1-02 and edition "Professional" [INFO] RC-Releasing staging repository with IDs=[jakartaauthorization-1007] Waiting for operation to complete... .. [INFO] Released [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Jakarta Authorization 3.0.0-SNAPSHOT ............... SKIPPED [INFO] Jakarta Authorization Specification 3.0-SNAPSHOT ... SKIPPED [INFO] Jakarta Authorization Parent 3.0.0-SNAPSHOT ........ SUCCESS [ 11.223 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 15.263 s [INFO] Finished at: 2023-12-07T20:04:40Z [INFO] ------------------------------------------------------------------------ $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 56 killed; [ssh-agent] Stopped. Finished: SUCCESS