Preparing Release Branch for next patch

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

00:00:07

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

00:07:29

 
  Containerize
passed aws-containerize #253888
osdu-medium

00:01:21

passed azure_containerize #253886
osdu-medium

00:01:25

passed osdu-gcp-containerize #253887

00:02:12

 
  Scan
passed bandit-sast #253891
osdu-medium

00:08:52

passed fossa-analyze #253889
osdu-medium

00:12:51

passed gemnasium-maven-dependency_scanning #253890
osdu-large

00:07:21

passed license_scanning #253893
osdu-medium

00:11:32

passed spotbugs-sast #253892
osdu-large

00:17:14

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

00:00:46

passed azure_deploy #253894
osdu-medium

00:01:12

passed ibm-deploy #253897
osdu-medium

00:03:47

passed osdu-gcp-deploy #253895

00:00:58

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

00:05:22

passed azure_test #253898
osdu-medium

00:15:47

passed ibm-test #253901
osdu-medium

00:05:36

passed osdu-gcp-test #253899
osdu-medium

00:11:30

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

00:00:29

passed fossa-report #253903
osdu-small

00:00:30

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

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