changed

8 jobs for users/nikhil/perfTestNotification in 17 minutes and 48 seconds (queued for 5 seconds)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #538168
osdu-small allowed to fail

00:00:06

failed deprecated-pipeline-include #538167
allowed to fail

00:00:07

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

00:04:34

 
  Scan
passed bandit-sast #538171
osdu-medium

00:03:12

passed gemnasium-maven-dependency_scanning #538170
osdu-medium

00:05:17

passed license_scanning #538174
osdu-medium

00:04:54

passed semgrep-sast #538172
osdu-medium

00:02:45

passed spotbugs-sast #538173
osdu-large

00:13:04

 
Name Stage Failure
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:021b3423115ff662225e83d7e2606475217de7b55fde83ce3447a54019a77aa2 for alpine:latest with digest alpine@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae ...
$ 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
failed
deprecated-pipeline-include .Pre
Removing testing/notification-test-gcp/target/
Removing testing/notification-test-ibm/target/

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ echo "$DEPRECATED_MSG"
The FOSSA scanner now supports different build environments, which should be specified directly. Consider using fossa-maven.yml instead.
$ /bin/false
ERROR: Job failed: exit code 1