fixing version conflict

8 jobs for users/amaverma/AdminApiwithSPAuthz in 36 minutes and 33 seconds (queued for 1 second)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #393039
osdu-small allowed to fail

00:00:06

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

00:07:32

 
  Scan
passed bandit-sast #393043
osdu-medium

00:07:09

passed gemnasium-maven-dependency_scanning #393041
osdu-large

00:07:39

passed gemnasium-python-dependency_scanning #393042
osdu-medium

00:07:20

passed license_scanning #393046
osdu-medium

00:07:47

passed semgrep-sast #393044
osdu-medium

00:06:56

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

00:28:52

 
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:d4ff818577bc193b309b355b02ebc9220427090057b54a59e73b79bdfe139b83 for alpine:latest with digest alpine@sha256:234cb88d3020898631af0ccbbcca9a66ae7306ecd30c9720690858c1b007d2a0 ...
$ 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