Merge branch 'ibm-limit-check' into 'master'

non zero check added on limit

See merge request !121
27 jobs for master in 47 minutes and 7 seconds (queued for 4 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #425606
osdu-small allowed to fail

00:00:08

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

00:07:30

 
  Containerize
passed aws-containerize #425608
osdu-medium

00:01:35

passed azure_containerize #425609
osdu-medium

00:01:03

passed osdu-gcp-containerize-gcloud #425610

00:02:25

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

00:00:45

 
  Scan
passed bandit-sast #425615
osdu-medium

00:07:14

passed fossa-analyze #425612
osdu-medium

00:10:58

passed gemnasium-maven-dependency_scanning #425613
osdu-large

00:08:39

passed gemnasium-python-dependency_scanning #425614
osdu-medium

00:08:16

passed license_scanning #425618
osdu-medium

00:07:17

passed semgrep-sast #425616
osdu-medium

00:06:27

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

00:14:54

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

00:00:08

passed azure_deploy #425621
osdu-medium

00:01:55

passed ibm-deploy #425620
osdu-medium

00:02:41

passed osdu-gcp-deploy #425622

00:00:50

 
  Bootstrap
passed aws_bootstrap #425624
osdu-medium

00:04:25

passed azure_bootstrap #425623

00:03:09

failed ibm_bootstrap #425625

00:00:51

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

00:10:48

passed azure_test #425628
osdu-medium

00:24:50

skipped ibm-test #425627
osdu-medium
passed osdu-gcp-test #425629
osdu-medium

00:35:59

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

00:00:37

passed fossa-report #425631
osdu-small

00:00:31

 
  Publish
skipped ibm-preship-promote #425632
osdu-medium
 
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
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=425630 responseStatus=201 Created token=5vFYF9hy
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
ibm_bootstrap Bootstrap
Error with kind osdu:wks:reference-data--WellInterestType:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
Error with kind osdu:wks:work-product-component--WellLog:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
Error with kind osdu:wks:master-data--Wellbore:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
Error with kind osdu:wks:work-product-component--WellboreMarkerSet:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
Error with kind osdu:wks:work-product-component--WellboreTrajectory:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
Error with kind osdu:wks:reference-data--WellboreTrajectoryType:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
Error with kind osdu:wks:reference-data--WordFormatType:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
Error with kind osdu:wks:work-product--WorkProduct:1.0.0: Message: Expecting value: line 1 column 1 (char 0)
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