merging with maste

8 jobs for users/amaverma/AdminAPIwithSystemAuthZ in 23 minutes and 41 seconds (queued for 2 seconds)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #388441
osdu-small allowed to fail

00:00:09

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

00:07:56

 
  Scan
passed bandit-sast #388445
osdu-medium

00:05:58

passed gemnasium-maven-dependency_scanning #388443
osdu-large

00:08:37

passed gemnasium-python-dependency_scanning #388444
osdu-medium

00:07:31

passed license_scanning #388448
osdu-medium

00:06:27

passed semgrep-sast #388446
osdu-medium

00:07:05

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

00:15:35

 
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:6dbb9cc54074106d46d4ccb330f2a40a682d49dda5f4844962b7dce9fe44aaec for alpine:latest with digest alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f ...
$ 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