Merge branch 'schema-notification-slb' into 'master'

Schema Notification

See merge request !103
27 jobs for master in 76 minutes and 26 seconds (queued for 2 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #350669
osdu-small allowed to fail

00:00:07

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

00:04:43

 
  Containerize
passed aws-containerize #350671
osdu-medium

00:02:46

passed azure_containerize #350672
osdu-medium

00:02:22

passed osdu-gcp-containerize-gcloud #350673

00:03:56

passed osdu-gcp-containerize-gitlab #350674
osdu-medium

00:01:57

 
  Scan
passed bandit-sast #350678
osdu-medium

00:03:55

passed fossa-analyze #350675
osdu-medium

00:12:16

passed gemnasium-maven-dependency_scanning #350676
osdu-large

00:06:40

passed gemnasium-python-dependency_scanning #350677
osdu-medium

00:03:23

passed license_scanning #350680
osdu-medium

00:02:53

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

00:45:00

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

00:00:40

passed azure_deploy #350683
osdu-medium

00:02:19

passed ibm-deploy #350682
osdu-medium

00:01:52

passed osdu-gcp-deploy #350753

00:01:41

failed osdu-gcp-deploy #350684

00:09:44

 
  Bootstrap
passed aws_bootstrap #350686
osdu-medium

00:02:02

passed azure_bootstrap #350685

00:02:18

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

00:03:55

passed azure_test #350754
osdu-medium

00:24:10

passed ibm-test #350688
osdu-medium

00:04:18

passed osdu-gcp-test #350690
osdu-medium

00:24:50

failed azure_test #350689
osdu-medium

00:23:02

 
  Attribution
failed fossa-check-notice #350691
osdu-small

00:00:42

passed fossa-report #350692
osdu-small

00:00:44

 
  Publish
passed ibm-preship-promote #350693
osdu-medium

00:00:15

 
Name Stage Failure
failed
fossa-check-notice Attribution
You can download the NOTICE file from this job's artifacts and directly commit it to the repository to resolve
this. Before doing so, review the differences to make sure that they make sense given the changes that you have
made. If they do not, reach out to a maintainer to help diagnose the issue.
Uploading artifacts for failed job
Uploading artifacts...
public: found 2 matching files and directories

Uploading artifacts as "archive" to coordinator... ok
id=350691 responseStatus=201 Created token=yAiMUXQm
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
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