Merge branch 'gcp-logs-it' into 'master'

Remove secrets from logs of Services during ITs (GONRG-3445)

See merge request !122
26 jobs for master in 26 minutes and 29 seconds (queued for 6 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #630139
osdu-small allowed to fail

00:01:32

failed deprecated-pipeline-include #630138
allowed to fail

00:00:07

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

00:08:49

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

00:00:09

 
  Containerize
passed aws-containerize #630145
osdu-medium

00:02:51

passed azure_containerize #630142
osdu-medium

00:02:37

passed osdu-gcp-containerize-gcloud #630143

00:02:05

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

00:02:06

 
  Scan
passed bandit-sast #630148
osdu-medium

00:06:59

passed fossa-analyze #630146
osdu-medium

00:13:46

passed gemnasium-maven-dependency_scanning #630147
osdu-medium

00:06:49

passed license_scanning #630151
osdu-medium

00:06:16

passed semgrep-sast #630149
osdu-medium

00:07:00

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

00:03:13

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

00:02:26

passed azure_deploy #630152
osdu-medium

00:03:53

failed ibm-deploy #630155
osdu-medium

00:00:00

passed ibm-deploy-devpri #630156
osdu-medium

00:09:52

passed osdu-gcp-deploy #630153

00:00:59

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

00:04:21

failed azure_test #630157
osdu-medium

00:05:44

skipped ibm-test #630160
osdu-medium
passed osdu-gcp-test #630158
osdu-medium

00:05:35

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

00:02:18

passed fossa-report #630162
osdu-small

00:02:18

 
  Publish
skipped ibm-preship-promote #630163
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=630161 responseStatus=201 Created token=xB_Ja8yz
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
azure_test Integration
Uploading artifacts...
WARNING: ./**/target/*.jar: no matching files
WARNING: ./**/maven-*-output.txt: no matching files
ERROR: No files to upload
Uploading artifacts...
testing/notification-test-azure/target/*/TEST-*.xml: found 2 matching files and directories

Uploading artifacts as "junit" to coordinator... ok
id=630157 responseStatus=201 Created token=H1q3AfNM
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 testing/notification-test-gcp/target/
Removing testing/notification-test-ibm/target/

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