Started by user Scott M Stark Rebuilds build #4 Running as Scott M Stark Agent basic-74ldg is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: labels: jenkins: "slave" jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd" jenkins/label: "basic" name: "basic-74ldg" namespace: "cdi" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.cdi.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "basic-74ldg" - 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-74ldg" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.cdi.svc.cluster.local/cdi/" 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-cdi" 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-74ldg (basic) in workspace /home/jenkins/agent/workspace/CDI-TCK-DistRelease-JDK17 [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-IuqIxaG9epIP/agent.48 SSH_AGENT_PID=50 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/CDI-TCK-DistRelease-JDK17@tmp/private_key_13223391094949773727.key (/home/jenkins/agent/workspace/CDI-TCK-DistRelease-JDK17@tmp/private_key_13223391094949773727.key) [ssh-agent] Using credentials genie.cdi (ssh://genie.cdi@projects-storage.eclipse.org) Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/CDI-TCK-DistRelease-JDK17@tmp/private_key_6081893846115713519.key (/home/jenkins/agent/workspace/CDI-TCK-DistRelease-JDK17@tmp/private_key_6081893846115713519.key) [ssh-agent] Using credentials eclipse-cdi-bot (GitHub bot SSH) The recommended git tool is: NONE using credential github-bot Cloning the remote Git repository Cloning repository https://github.com/jakartaee/cdi-tck > git init /home/jenkins/agent/workspace/CDI-TCK-DistRelease-JDK17/cdi-tck # timeout=10 Fetching upstream changes from https://github.com/jakartaee/cdi-tck > git --version # timeout=10 > git --version # 'git version 2.20.1' using GIT_ASKPASS to set credentials GitHub bot (username/token) > git fetch --tags --force --progress -- https://github.com/jakartaee/cdi-tck +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/jakartaee/cdi-tck # 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 65d4d1de1be2028d8be0859de7429025b12d4896 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 65d4d1de1be2028d8be0859de7429025b12d4896 # timeout=10 > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master 65d4d1de1be2028d8be0859de7429025b12d4896 # timeout=10 Commit message: "Update 4.1.0-M1 tag" > git rev-list --no-walk f4de9220e02f6830c480c67f17586ff121d70ca0 # timeout=10 [CDI-TCK-DistRelease-JDK17] $ /bin/bash -e /tmp/jenkins8714217158724417633.sh gpg: directory '/home/jenkins/.gnupg' created gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created gpg: key 928B20E9AD5298CC: public key "Jakarta Contexts and Dependency Injection <cdi-dev@eclipse.org>" imported gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status gpg: key 928B20E9AD5298CC: secret key imported gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: secret keys imported: 1 Secret subkeys are available. pub rsa4096/928B20E9AD5298CC created: 2019-07-24 expires: 2024-07-22 usage: SCEA trust: unknown validity: unknown ssb rsa4096/0AA3E5C3D232E79B created: 2019-07-24 expires: 2024-07-22 usage: S [ unknown] (1). Jakarta Contexts and Dependency Injection <cdi-dev@eclipse.org> pub rsa4096/928B20E9AD5298CC created: 2019-07-24 expires: 2024-07-22 usage: SCEA trust: unknown validity: unknown ssb rsa4096/0AA3E5C3D232E79B created: 2019-07-24 expires: 2024-07-22 usage: S [ unknown] (1). Jakarta Contexts and Dependency Injection <cdi-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/928B20E9AD5298CC created: 2019-07-24 expires: 2024-07-22 usage: SCEA trust: ultimate validity: unknown ssb rsa4096/0AA3E5C3D232E79B created: 2019-07-24 expires: 2024-07-22 usage: S [ unknown] (1). Jakarta Contexts and Dependency Injection <cdi-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 2024-07-22 pub rsa4096/928B20E9AD5298CC created: 2019-07-24 expires: 2024-07-22 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/0AA3E5C3D232E79B created: 2019-07-24 expires: 2024-07-22 usage: S [ultimate] (1). Jakarta Contexts and Dependency Injection <cdi-dev@eclipse.org> pub rsa4096/928B20E9AD5298CC created: 2019-07-24 expires: 2024-07-22 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/0AA3E5C3D232E79B created: 2019-07-24 expires: 2024-07-22 usage: S [ultimate] (1). Jakarta Contexts and Dependency Injection <cdi-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/928B20E9AD5298CC created: 2019-07-24 expires: 2024-07-22 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/0AA3E5C3D232E79B created: 2019-07-24 expires: 2024-07-22 usage: S [ultimate] (1). Jakarta Contexts and Dependency Injection <cdi-dev@eclipse.org> [CDI-TCK-DistRelease-JDK17] $ /bin/bash -ex /tmp/jenkins4481014553211281087.sh + TOOLS_PREFIX=/opt/tools + MVN_HOME=/opt/tools/apache-maven/latest + PATH=/opt/tools/apache-maven/latest/bin:/opt/tools/java/openjdk/jdk-17/latest/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + /opt/tools/java/openjdk/jdk-17/latest/bin/java -version openjdk version "17.0.2" 2022-01-18 OpenJDK Runtime Environment (build 17.0.2+8-86) OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing) + cd cdi-tck + git status On branch master nothing to commit, working tree clean ++ mvn -version + TEST_MVN='Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Maven home: /opt/tools/apache-maven/latest Java version: 17.0.2, vendor: Oracle Corporation, runtime: /opt/tools/java/openjdk/jdk-17/17.0.2+8 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.18.5-100.fc35.x86_64", arch: "amd64", family: "unix"' + echo 'Maven version: Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Maven home: /opt/tools/apache-maven/latest Java version: 17.0.2, vendor: Oracle Corporation, runtime: /opt/tools/java/openjdk/jdk-17/17.0.2+8 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.18.5-100.fc35.x86_64", arch: "amd64", family: "unix"' Maven version: Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Maven home: /opt/tools/apache-maven/latest Java version: 17.0.2, vendor: Oracle Corporation, runtime: /opt/tools/java/openjdk/jdk-17/17.0.2+8 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.18.5-100.fc35.x86_64", arch: "amd64", family: "unix" + RELEASE_TAG=4.1.0-M1 + SPEC_VERSION=4.1 + echo 'Release version: 4.1.0-M1' Release version: 4.1.0-M1 + echo 'Spec version: 4.1' Spec version: 4.1 + git config --global user.email cdi-bot@eclipse.org + git config --global user.name 'Eclipse CDI Bot' + echo 'Checking out 4.1.0-M1...' Checking out 4.1.0-M1... + git checkout 4.1.0-M1 Note: checking out '4.1.0-M1'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 65d4d1de1 Update 4.1.0-M1 tag + git status HEAD detached at 4.1.0-M1 nothing to commit, working tree clean + PROFILE= + [[ true = \t\r\u\e ]] + PROFILE=-Pstaging + echo '-[ Executing dist upload ]----------------------------------------------------------' -[ Executing dist upload ]---------------------------------------------------------- + cd dist-build + mvn -Pstaging -Drelease package [INFO] Scanning for projects... [INFO] Artifact org.eclipse.ee4j:project:pom:1.0.9 is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from [jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public, default, releases), sonatype-nexus-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/, default, releases), eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/, default, releases)] [INFO] Artifact org.eclipse.ee4j:project:pom:1.0.9 is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from [jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public, default, releases), sonatype-nexus-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/, default, releases), eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/, default, releases)] [WARNING] [WARNING] Some problems were encountered while building the effective model for jakarta.enterprise:cdi-tck-dist-porting-package:pom:4.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-deploy-plugin is missing. @ line 76, column 21 [WARNING] [WARNING] Some problems were encountered while building the effective model for jakarta.enterprise:cdi-tck-dist-libs:pom:4.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-deploy-plugin is missing. @ line 37, column 21 [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] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] CDI TCK Distribution - Weld Porting Package [pom] [INFO] CDI TCK Distribution - Libraries [pom] [INFO] CDI TCK Distribution [pom] [INFO] [INFO] ----------< jakarta.enterprise:cdi-tck-dist-porting-package >----------- [INFO] Building CDI TCK Distribution - Weld Porting Package 4.1.0-SNAPSHOT [1/3] [INFO] from porting-package/pom.xml [INFO] --------------------------------[ pom ]--------------------------------- [WARNING] The POM for jakarta.enterprise:cdi-tck-api:jar:4.1.0-SNAPSHOT is missing, no dependency information available [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] CDI TCK Distribution - Weld Porting Package 4.1.0-SNAPSHOT FAILURE [ 22.000 s] [INFO] CDI TCK Distribution - Libraries 4.1.0-SNAPSHOT .... SKIPPED [INFO] CDI TCK Distribution 4.1.0-M1 ...................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 24.659 s [INFO] Finished at: 2023-12-01T00:24:00Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project cdi-tck-dist-porting-package: Could not resolve dependencies for project jakarta.enterprise:cdi-tck-dist-porting-package:pom:4.1.0-SNAPSHOT: The following artifacts could not be resolved: jakarta.enterprise:cdi-tck-api:jar:4.1.0-SNAPSHOT (absent): Could not find artifact jakarta.enterprise:cdi-tck-api:jar:4.1.0-SNAPSHOT -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 50 killed; [ssh-agent] Stopped. Archiving artifacts Finished: FAILURE