Merge remote-tracking branch 'origin/dev' into aws-eks

24 jobs for aws-eks in 22 minutes and 30 seconds (queued for 5 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #541312
osdu-small allowed to fail

00:00:07

failed deprecated-pipeline-include #541311
allowed to fail

00:00:07

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

00:07:21

 
  Containerize
passed aws-containerize #541317
osdu-medium

00:02:43

passed azure_containerize #541314
osdu-medium

00:02:34

passed osdu-gcp-containerize-gcloud #541315

00:02:07

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

00:02:05

 
  Scan
passed bandit-sast #541320
osdu-medium

00:04:09

passed fossa-analyze #541318
osdu-medium

00:11:54

passed gemnasium-maven-dependency_scanning #541319
osdu-medium

00:06:34

passed license_scanning #541323
osdu-medium

00:06:07

passed semgrep-sast #541321
osdu-medium

00:04:51

passed spotbugs-sast #541322
osdu-large

00:14:57

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

00:02:22

passed azure_deploy #541324
osdu-medium

00:03:30

failed ibm-deploy #541327
osdu-medium

00:00:00

passed ibm-deploy-devpri #541328
osdu-medium

00:09:08

passed osdu-gcp-deploy #541325

00:00:59

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

00:04:13

failed azure_test #541329
osdu-medium

00:06:20

skipped ibm-test #541332
osdu-medium
passed osdu-gcp-test #541330
osdu-medium

00:05:01

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

00:02:16

passed fossa-report #541334
osdu-small

00:02:37

 
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=541333 responseStatus=201 Created token=wgZCV84f
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=541329 responseStatus=201 Created token=x4EZneVw
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
Reinitialized existing Git repository in /builds/osdu/platform/system/notification/.git/
Checking out 219bfc03 as aws-eks...

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