Merge branch 'IBM-upgrade-core-lib-version' into 'master'

Ibm upgrade core lib version

See merge request !126
27 jobs for master in 30 minutes and 25 seconds (queued for 10 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #673375
osdu-small allowed to fail

00:00:06

failed deprecated-gcp-pipeline #673374
allowed to fail

00:00:09

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

00:08:41

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

00:00:07

 
  Containerize
passed aws-containerize #673378
osdu-medium

00:01:07

passed azure_containerize #673380
osdu-medium

00:01:26

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

00:01:11

 
  Scan
passed bandit-sast #673383
osdu-medium

00:03:16

passed fossa-analyze #673381
osdu-medium

00:16:50

passed gemnasium-maven-dependency_scanning #673382
osdu-medium

00:05:06

passed license_scanning #673386
osdu-medium

00:09:59

passed semgrep-sast #673384
osdu-medium

00:07:09

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

00:03:22

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

00:00:35

passed azure_deploy #673392
osdu-medium

00:03:38

passed ibm-deploy #673451
osdu-medium

00:07:53

failed ibm-deploy-devpri #673389
osdu-medium

00:04:03

passed osdu-gcp-deploy-configmap #673390

00:00:47

passed osdu-gcp-deploy-deployment #673391

00:00:22

failed ibm-deploy #673388
osdu-medium

00:00:05

 
  Integration
failed aws-test-java #673393
osdu-medium

00:02:25

passed azure_test #673396
osdu-medium

00:16:12

passed ibm-test #673394
osdu-medium

00:07:03

passed osdu-gcp-test #673395
osdu-medium

00:06:09

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

00:01:07

passed fossa-report #673398
osdu-small

00:00:34

 
  Publish
passed ibm-preship-promote #673399
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=673397 responseStatus=201 Created token=djFfYDAM
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
aws-test-java Integration
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
**** Showing the last 200 lines of the failed build (above). See Job artifacts for full log details *****

Uploading artifacts for failed job
Uploading artifacts...
testing/register-test-aws: found 98 matching files and directories

Uploading artifacts as "archive" to coordinator... ok
id=673393 responseStatus=201 Created token=NCBTq8xq
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
ibm-deploy-devpri Deploy The deployment job is older than the previously succeeded deployment job, and therefore cannot be run

Using project "og-cicd".
$ oc project $IBM_OPENSHIFT_DEVPRI_PROJECT
Already on project "og-cicd" on server "https://c103-e.us-south.containers.cloud.ibm.com:31778".
$ oc get bc/$CI_PROJECT_NAME 2> /dev/null || oc new-build --name $CI_PROJECT_NAME --binary --strategy source --image-stream openshift/ubi8-openjdk-8:1.3-15
NAME TYPE FROM LATEST
register Source Binary 33
$ oc start-build $CI_PROJECT_NAME --from-dir=. --follow
Uploading directory "." as binary input for the build ...
............................
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
deprecated-gcp-pipeline .Pre
Removing helm.tgz
Removing linux-amd64/

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ echo "$DEPRECATED_MSG"
The integration test environment previously managed by the cloud-providers/gcp.yml is no longer supported. Consider removing it from your .gitlab-ci.yml
$ /bin/false
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: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