There is a security vulnerability in SSH key-generation using GitKraken < v8.0.1. If you used this tool to create SSH keys, please update GitKraken and regenerate. If you need help with this, contact forum-support@opengroup.org

Updating FOSSA NOTICE

26 jobs for update-dependencies in 51 minutes and 2 seconds (queued for 13 seconds)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #552172
osdu-small allowed to fail

00:00:09

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

00:10:22

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

00:01:45

 
  Containerize
passed aws-containerize #552175
osdu-medium

00:06:02

passed azure_containerize #552176
osdu-medium

00:06:14

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

00:05:38

 
  Scan
passed bandit-sast #552180
osdu-medium

00:10:39

passed fossa-analyze #552178
osdu-medium

00:17:46

passed gemnasium-maven-dependency_scanning #552179
osdu-medium

00:13:14

passed license_scanning #552184
osdu-medium

00:09:25

passed security-code-scan-sast #552181
osdu-medium

00:10:36

passed semgrep-sast #552182
osdu-medium

00:11:19

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

00:08:22

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

00:01:26

passed azure_deploy #552187
osdu-medium

00:10:47

passed ibm-deploy #552186
osdu-medium

00:04:47

passed osdu-gcp-deploy-configmap #552188

00:03:16

passed osdu-gcp-deploy-deployment #552189

00:00:41

 
  Integration
passed aws-test-java #552190
aws-internal-test

00:02:14

passed azure_test #552192
osdu-medium

00:15:21

passed ibm-test #552191
osdu-medium

00:13:37

failed osdu-gcp-test #552540
osdu-medium

00:07:43

failed osdu-gcp-test #552193
osdu-medium

00:07:52

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

00:00:44

passed fossa-report #552195
osdu-small

00:00:39

failed fossa-check-notice #552194
osdu-small

00:00:56

 
Name Stage Failure
failed
osdu-gcp-test Integration
Uploading artifacts...
test-results.log: found 1 matching files and directories

WARNING: testing/search-test-gcp/target/*/TEST-*.xml: no matching files
Uploading artifacts as "archive" to coordinator... ok
id=552540 responseStatus=201 Created token=uhuxFyq8
Uploading artifacts...
WARNING: testing/search-test-gcp/target/*/TEST-*.xml: no matching files
ERROR: No files to upload
Cleaning up file based variables
ERROR: Job failed: exit code 1
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=552539 responseStatus=201 Created token=BMCNq3dN
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-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