Creating Release Commit

8 jobs for smanjunath/resolve_governanceIssues in 22 minutes and 39 seconds (queued for 10 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #602664
osdu-small allowed to fail

00:00:19

 
  Build
passed compile-and-unit-test #602665
osdu-medium

00:10:17

passed osdu-gcp-helm-charts #602666
osdu-small

00:01:29

 
  Scan
passed bandit-sast #602668
osdu-medium

00:09:35

passed gemnasium-maven-dependency_scanning #602667
osdu-medium

00:10:47

passed license_scanning #602671
osdu-medium

00:12:00

passed semgrep-sast #602669
osdu-medium

00:08:05

failed spotbugs-sast #602670
osdu-large allowed to fail

00:06:25

 
Name Stage Failure
failed
spotbugs-sast Scan
Running after_script
Running after script...
$ tar -cC ~/.m2 repository | tar -xC $CI_PROJECT_DIR/.m2
Uploading artifacts for failed job
Uploading artifacts...
WARNING: gl-sast-report.json: no matching files
ERROR: No files to upload
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab for alpine:latest with digest alpine@sha256:e1c082e3d3c45cccac829840a25941e679c25d438cc8412c2fa221cf1a824e6a ...
$ echo "$DEPRECATED_MSG"
The AWS includes now support different build environments, which should be specified directly. Consider using: aws-global.yml, and either aws-maven.yml or aws-python.yml
$ /bin/false
Cleaning up file based variables
ERROR: Job failed: exit code 1