Preparing Release Branch for next patch

20 jobs for release/0.5 in 20 minutes and 33 seconds (queued for 2 seconds)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-pipeline-include #201783
allowed to fail

00:00:08

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

00:05:39

 
  Containerize
passed aws-containerize #201787
osdu-medium

00:05:57

passed azure_containerize #201785
osdu-medium

00:02:23

passed osdu-gcp-containerize #201786

00:02:23

 
  Scan
passed bandit-sast #201790
osdu-medium

00:05:52

passed fossa-analyze #201788
osdu-medium

00:11:26

passed gemnasium-maven-dependency_scanning #201789
osdu-large

00:04:38

passed license_scanning #201792
osdu-medium

00:05:38

passed spotbugs-sast #201791
osdu-large

00:13:28

 
  Deploy
passed aws-update-ecs #201795
osdu-medium

00:04:21

passed azure_deploy #201793
osdu-medium

00:00:50

passed ibm-deploy #201796
osdu-medium

00:03:18

passed osdu-gcp-deploy #201794

00:01:01

 
  Integration
passed aws-test-java #201799
osdu-medium

00:04:19

passed azure_test #201797
osdu-medium

00:10:08

passed ibm-test #201800
osdu-medium

00:04:56

passed osdu-gcp-test #201798
osdu-medium

00:05:32

 
  Attribution
passed fossa-check-notice #201801
osdu-small

00:02:26

passed fossa-report #201802
osdu-small

00:02:22

 
Name Stage Failure
failed
deprecated-pipeline-include .Pre
Reinitialized existing Git repository in /builds/osdu/platform/system/notification/.git/
Checking out c07ef987 as release/0.5...

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