gemnasium-maven-dependency_scanning
Failed Started
by
@rihtajo
Joze RIHTARSIC
1Running with gitlab-runner 15.6.1 (133d7e76)2 on edelquality docker runner without Docker in docker mode ZcvQMEgp5Using Docker executor with image registry.gitlab.com/security-products/gemnasium-maven:4 ...6Pulling docker image registry.gitlab.com/security-products/gemnasium-maven:4 ...7Using docker image sha256:0eadb65a27f9dfd6ee781e2cdfa19b333d8c2f5b3d76f81209acfa0344c48e96 for registry.gitlab.com/security-products/gemnasium-maven:4 with digest registry.gitlab.com/security-products/gemnasium-maven@sha256:9a71ca7c363ff47c52cb178f27720aba6d92be04dc928dc1449b88dd6bb4a642 ...9Running on runner-zcvqmegp-project-162-concurrent-2 via edelquality...11Fetching changes with git depth set to 20...12Reinitialized existing Git repository in /tmp/builds/ZcvQMEgp/2/edelivery/smp/.git/13Checking out 72da2eb4 as development...14Removing gl-dependency-scanning-report.json15Removing retire-jsrepository.json16Removing sbom-manifest.json17Removing smp-angular/gl-sbom-npm-npm.cdx.json18Skipping Git submodules setup20Using docker image sha256:0eadb65a27f9dfd6ee781e2cdfa19b333d8c2f5b3d76f81209acfa0344c48e96 for registry.gitlab.com/security-products/gemnasium-maven:4 with digest registry.gitlab.com/security-products/gemnasium-maven@sha256:9a71ca7c363ff47c52cb178f27720aba6d92be04dc928dc1449b88dd6bb4a642 ...21$ /analyzer run22Using java version 'adoptopenjdk-8.0.252+9.1'23Using gradle version '6.7.1'24[INFO] [gemnasium-maven] [2023-11-20T07:34:31Z] ▶ GitLab gemnasium-maven analyzer v4.9.025[INFO] [gemnasium-maven] [2023-11-20T07:34:31Z] ▶ Detected supported dependency files in '.'. Dependency files detected in this directory will be processed. Dependency files in other directories will be skipped.26exit status 128Uploading artifacts...29WARNING: **/gl-sbom-*.cdx.json: no matching files. Ensure that the artifact path is relative to the working directory 30ERROR: No files to upload 31Uploading artifacts...32WARNING: gl-dependency-scanning-report.json: no matching files. Ensure that the artifact path is relative to the working directory 33ERROR: No files to upload 35ERROR: Job failed: exit code 1