Merge branch 'users/nikhil/fixCoreCommon' into 'master'

fix core lib and common

See merge request !133
26 jobs for master in 40 minutes and 37 seconds (queued for 5 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #672901
osdu-small allowed to fail

00:00:07

failed deprecated-pipeline-include #672900
allowed to fail

00:00:06

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

00:07:24

passed osdu-gcp-helm-charts #672903
osdu-small

00:01:08

 
  Containerize
passed aws-containerize #672906
osdu-medium

00:01:32

passed azure_containerize #672904
osdu-medium

00:02:48

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

00:00:53

 
  Scan
passed bandit-sast #672909
osdu-medium

00:06:05

passed fossa-analyze #672907
osdu-medium

00:32:26

failed gemnasium-maven-dependency_scanning #672908
osdu-medium allowed to fail

00:03:05

passed license_scanning #672912
osdu-medium

00:02:53

passed semgrep-sast #672910
osdu-medium

00:05:35

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

00:02:37

 
  Deploy
passed aws-update-eks #672916
osdu-medium

00:01:02

passed azure_deploy #672913
osdu-medium

00:02:25

failed ibm-deploy #672917
osdu-medium

00:00:00

passed ibm-deploy-devpri #672918
osdu-medium

00:08:32

passed osdu-gcp-deploy-configmap #672914

00:01:02

passed osdu-gcp-deploy-deployment #672915

00:00:25

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

00:04:30

passed azure_test #672919
osdu-medium

00:12:52

skipped ibm-test #672922
osdu-medium
passed osdu-gcp-test #672920
osdu-medium

00:04:13

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

00:00:32

passed fossa-report #672924
osdu-small

00:00:27

 
  Publish
skipped ibm-preship-promote #672925
osdu-medium
 
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=672923 responseStatus=201 Created token=uN-j8zEU
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
gemnasium-maven-dependency_scanning 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-dependency-scanning-report.json: no matching files
ERROR: No files to upload
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
failed
ibm-deploy Deploy The deployment job is older than the previously succeeded deployment job, and therefore cannot be run
No job log
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab for alpine:latest with digest alpine@sha256:e1c082e3d3c45cccac829840a25941e679c25d438cc8412c2fa221cf1a824e6a ...
$ 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 helm.tgz
Removing linux-amd64/

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