Merge branch 'aws-xuserid-fix' into 'master'

istio related fix

See merge request !129
28 jobs for master in 24 minutes and 15 seconds (queued for 6 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #680971
osdu-small allowed to fail

00:00:06

failed deprecated-gcp-pipeline #680970
allowed to fail

00:00:08

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

00:06:26

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

00:00:09

 
  Containerize
passed aws-containerize #680974
osdu-medium

00:00:56

passed azure_containerize #680976
osdu-medium

00:01:14

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

00:01:03

 
  Scan
passed bandit-sast #680979
osdu-medium

00:03:14

passed fossa-analyze #680977
osdu-medium

00:08:30

passed gemnasium-maven-dependency_scanning #680978
osdu-medium

00:05:22

passed license_scanning #680982
osdu-medium

00:04:35

passed semgrep-sast #680980
osdu-medium

00:03:21

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

00:03:10

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

00:00:31

passed azure_deploy #680988
osdu-medium

00:02:21

passed ibm-deploy #681018
osdu-medium

00:03:24

passed ibm-deploy-devpri #680985
osdu-medium

00:02:48

passed osdu-gcp-deploy-configmap #680986

00:00:55

passed osdu-gcp-deploy-deployment #680987

00:00:34

failed ibm-deploy #680984
osdu-medium

00:00:00

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

00:03:13

passed azure_test #680992
osdu-medium

00:13:24

passed ibm-test #680990
osdu-medium

00:04:55

passed osdu-gcp-test #680991
osdu-medium

00:04:09

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

00:00:33

passed fossa-report #680994
osdu-small

00:00:42

failed fossa-check-notice #680993
osdu-small

00:01:53

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

00:00:19

 
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=681174 responseStatus=201 Created token=-x7DfDff
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
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