Started by user arjan tijms Running as arjan tijms Agent basic-kd8wl is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: annotations: {} labels: jenkins: "slave" jenkins/label: "" name: "basic-kd8wl" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.es.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "basic-kd8wl" - 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-kd8wl" - 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-kd8wl in workspace /home/jenkins/agent/workspace/1_security-build-and-stage [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-D8lGk1cwyQKx/agent.84 SSH_AGENT_PID=86 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/1_security-build-and-stage@tmp/private_key_2073243029044169239.key (/home/jenkins/agent/workspace/1_security-build-and-stage@tmp/private_key_2073243029044169239.key) [ssh-agent] Using credentials eclipse-es-bot (GitHub bot SSH) using credential github-bot-ssh Cloning the remote Git repository Cloning repository git@github.com:eclipse-ee4j/security-api.git > git init /home/jenkins/agent/workspace/1_security-build-and-stage # timeout=10 Fetching upstream changes from git@github.com:eclipse-ee4j/security-api.git > git --version # timeout=10 using GIT_SSH to set credentials GitHub bot SSH > git fetch --tags --force --progress -- git@github.com:eclipse-ee4j/security-api.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url git@github.com:eclipse-ee4j/security-api.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url git@github.com:eclipse-ee4j/security-api.git # timeout=10 Fetching upstream changes from git@github.com:eclipse-ee4j/security-api.git using GIT_SSH to set credentials GitHub bot SSH > git fetch --tags --force --progress -- git@github.com:eclipse-ee4j/security-api.git +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 b60e84b8520ca29f9ae94f61baa156dfb29aac7e (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b60e84b8520ca29f9ae94f61baa156dfb29aac7e # timeout=10 Commit message: "Back to snapshot" > git rev-list --no-walk b60e84b8520ca29f9ae94f61baa156dfb29aac7e # timeout=10 [1_security-build-and-stage] $ /bin/bash -e /tmp/jenkins5804803980483609583.sh gpg: directory '/home/jenkins/.gnupg' created gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created gpg: key 01061A667879AAD9: 1 signature not checked due to a missing key gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created gpg: key 01061A667879AAD9: public key "Eclipse Project for Enterprise Security <es-dev@eclipse.org>" imported gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status gpg: key 01061A667879AAD9: 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 Secret subkeys are available. pub rsa4096/01061A667879AAD9 created: 2018-10-03 expires: 2023-10-02 usage: SCEA trust: unknown validity: unknown ssb rsa4096/07280E9E11DF5A43 created: 2018-10-03 expires: 2023-10-02 usage: S [ unknown] (1). Eclipse Project for Enterprise Security <es-dev@eclipse.org> pub rsa4096/01061A667879AAD9 created: 2018-10-03 expires: 2023-10-02 usage: SCEA trust: unknown validity: unknown ssb rsa4096/07280E9E11DF5A43 created: 2018-10-03 expires: 2023-10-02 usage: S [ unknown] (1). Eclipse Project for Enterprise Security <es-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/01061A667879AAD9 created: 2018-10-03 expires: 2023-10-02 usage: SCEA trust: ultimate validity: unknown ssb rsa4096/07280E9E11DF5A43 created: 2018-10-03 expires: 2023-10-02 usage: S [ unknown] (1). Eclipse Project for Enterprise Security <es-dev@eclipse.org> Please note that the shown key validity is not necessarily correct unless you restart the program. 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-10-02 pub rsa4096/01061A667879AAD9 created: 2018-10-03 expires: 2023-10-02 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/07280E9E11DF5A43 created: 2018-10-03 expires: 2023-10-02 usage: S [ultimate] (1). Eclipse Project for Enterprise Security <es-dev@eclipse.org> pub rsa4096/01061A667879AAD9 created: 2018-10-03 expires: 2023-10-02 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/07280E9E11DF5A43 created: 2018-10-03 expires: 2023-10-02 usage: S [ultimate] (1). Eclipse Project for Enterprise Security <es-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/01061A667879AAD9 created: 2018-10-03 expires: 2023-10-02 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/07280E9E11DF5A43 created: 2018-10-03 expires: 2023-10-02 usage: S [ultimate] (1). Eclipse Project for Enterprise Security <es-dev@eclipse.org> [1_security-build-and-stage] $ /bin/bash -e /tmp/jenkins4267125430156329156.sh [1_security-build-and-stage] $ /bin/bash -e /tmp/jenkins371580304644094151.sh [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for jakarta.security.enterprise:jakarta.security.enterprise-api:bundle:2.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 185, column 29 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.eclipse.ee4j.security.enterprise-api:security-spec:pom:2.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 185, column 29 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 197, column 29 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.eclipse.ee4j.security.enterprise-api:security.enterprise-api-parent:pom:2.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 185, column 29 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 197, column 29 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] Inspecting build with total of 3 modules... [INFO] Installing Nexus Staging features: [INFO] ... total of 3 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Jakarta Security [bundle] [INFO] Jakarta Security Parent [pom] [INFO] Jakarta Security Specification [pom] [INFO] [INFO] --< org.eclipse.ee4j.security.enterprise-api:security.enterprise-api-parent >-- [INFO] Building Jakarta Security Parent 2.0.0-SNAPSHOT [1/3] [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- nexus-staging-maven-plugin:1.6.8:rc-list (default-cli) @ security.enterprise-api-parent --- [INFO] + Using server credentials "ossrh" from Maven settings. [INFO] * Connected to Nexus at https://jakarta.oss.sonatype.org:443/, is version 2.14.19-01 and edition "Professional" [INFO] Getting list of available staging repositories... [INFO] [INFO] ID State Description [INFO] jakartasecurityenterprise-1003 CLOSED jakarta.security.enterprise:jakarta.security.enterprise-api:2.0.0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for Jakarta Security Parent 2.0.0-SNAPSHOT: [INFO] [INFO] Jakarta Security ................................... SKIPPED [INFO] Jakarta Security Parent ............................ SUCCESS [ 1.079 s] [INFO] Jakarta Security Specification ..................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:04 min [INFO] Finished at: 2020-11-13T14:47:28Z [INFO] ------------------------------------------------------------------------ [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for jakarta.security.enterprise:jakarta.security.enterprise-api:bundle:2.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 185, column 29 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.eclipse.ee4j.security.enterprise-api:security-spec:pom:2.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 185, column 29 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 197, column 29 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.eclipse.ee4j.security.enterprise-api:security.enterprise-api-parent:pom:2.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 185, column 29 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing. @ org.eclipse.ee4j:project:1.0.6, /home/jenkins/.m2/repository/org/eclipse/ee4j/project/1.0.6/project-1.0.6.pom, line 197, column 29 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] Inspecting build with total of 3 modules... [INFO] Installing Nexus Staging features: [INFO] ... total of 3 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Jakarta Security [bundle] [INFO] Jakarta Security Parent [pom] [INFO] Jakarta Security Specification [pom] [INFO] [INFO] --< org.eclipse.ee4j.security.enterprise-api:security.enterprise-api-parent >-- [INFO] Building Jakarta Security Parent 2.0.0-SNAPSHOT [1/3] [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- nexus-staging-maven-plugin:1.6.8:rc-list-profiles (default-cli) @ security.enterprise-api-parent --- [INFO] + Using server credentials "ossrh" from Maven settings. [INFO] * Connected to Nexus at https://jakarta.oss.sonatype.org:443/, is version 2.14.19-01 and edition "Professional" [INFO] Getting list of available staging profiles... [INFO] [INFO] ID Mode Name [INFO] 3bdea18b0903 BOTH jakarta.security.enterprise [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for Jakarta Security Parent 2.0.0-SNAPSHOT: [INFO] [INFO] Jakarta Security ................................... SKIPPED [INFO] Jakarta Security Parent ............................ SUCCESS [ 0.895 s] [INFO] Jakarta Security Specification ..................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2.078 s [INFO] Finished at: 2020-11-13T14:47:30Z [INFO] ------------------------------------------------------------------------ [1_security-build-and-stage] $ /bin/bash -ex /tmp/jenkins776635253690073578.sh + '[' false = true ']' + '[' true = true ']' + exit 0 $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 86 killed; [ssh-agent] Stopped. Finished: SUCCESS