Started by upstream project "build-scripts/jobs/jdk17u/jdk17u-aix-ppc64-temurin" build number 457 originally caused by: Started by upstream project "build-scripts/openjdk17-pipeline" build number 1016 originally caused by: Started by upstream project "build-scripts/utils/betaTrigger_17ea" build number 478 originally caused by: Started by timer Running as SYSTEM Building remotely on jenkins-hetzner-worker (jsfsignX git-hg gpgsign worker master) in workspace /home/jenkins/workspace/sbom_validator_job [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... The recommended git tool is: git No credentials specified Cloning the remote Git repository Cloning repository https://github.com/adoptium/temurin-build > git init /home/jenkins/workspace/sbom_validator_job/temurin-build # timeout=10 Fetching upstream changes from https://github.com/adoptium/temurin-build > git --version # timeout=10 > git --version # 'git version 2.43.0' > git fetch --tags --force --progress -- https://github.com/adoptium/temurin-build +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/adoptium/temurin-build # 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 a442b3d5735489c0b36771e1f6da41ec472604ee (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a442b3d5735489c0b36771e1f6da41ec472604ee # timeout=10 Commit message: "Correctly set CONFIGURE_ARGS that was used in make exploded when running assmble exploded (#4380)" > git rev-list --no-walk a442b3d5735489c0b36771e1f6da41ec472604ee # timeout=10 Copied 2 artifacts from "build-scripts » jobs » jdk17u » jdk17u-aix-ppc64-temurin" build number 457 [sbom_validator_job] $ /bin/sh -xe /tmp/jenkins8874975248869357419.sh + ls /home/jenkins/workspace/sbom_validator_job/sboms OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea.json OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea-metadata.json + ls -1 /home/jenkins/workspace/sbom_validator_job/sboms/OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea-metadata.json /home/jenkins/workspace/sbom_validator_job/sboms/OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea.json + grep -v metadata + sh /home/jenkins/workspace/sbom_validator_job/temurin-build/tooling/validateSBOM.sh 17 jdk-17.0.19+1_adopt /home/jenkins/workspace/sbom_validator_job/sboms/OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea.json validateSBOM.sh: Setting up workspace directory /home/jenkins/workspace/sbom_validator_job/sbom_validation validateSBOM.sh: Downloading CycloneDX CLI binary ... validateSBOM.sh: Downloaded CycloneDX CLI binary to 'cyclonedx-linux-x64' validateSBOM.sh: SBOM validation start. validateSBOM.sh: Running general SBOM validation from https://github.com/CycloneDX/cyclonedx-cli validateSBOM.sh: Running cyclonedx-linux-x64 ... Command: "/home/jenkins/workspace/sbom_validator_job/sbom_validation/cyclonedx-linux-x64" validate --input-file "/home/jenkins/workspace/sbom_validator_job/sboms/OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea.json" --input-format json BOM validated successfully. validateSBOM.sh: Passed CycloneDX validation check. validateSBOM.sh: Running command: sh validateSBOMcontent.sh "/home/jenkins/workspace/sbom_validator_job/sboms/OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea.json" "17" "jdk-17.0.19+1_adopt" /home/jenkins/workspace/sbom_validator_job/sboms/OpenJDK17U-sbom_ppc64_aix_hotspot_17.0.19_1-ea.json BOOTJDK is 17.0.4-beta+7-202206162339 FREETYPE is 2.13.3 Checking for JDK source SHA validity... 9eae9c497411c6e75e501ea2b06316f71fe9e4fa refs/heads/release 9eae9c497411c6e75e501ea2b06316f71fe9e4fa refs/tags/jdk-17.0.19+1_adopt^{} SBOM SHA is a valid repository tag commit SHA: 9eae9c497411c6e75e501ea2b06316f71fe9e4fa Checking for temurin-build SHA validity: Checking for temurin-build SHA a2382c4fa2044e0094db987279f2f814039ce5af in https://github.com/adoptium/temurin-build WARNING: temurin-build SHA check failed. This can happen if it was not a tagged level. This can also happen with a branch being used and not a tag as we do for GAs so not failing. Note: As this is a warning message this will not cause a non-zero return code by itself. validateSBOMcontent.sh: PASSED SBOM validation complete. validateSBOM.sh: SBOM validation complete. [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] done Finished: SUCCESS