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

Update pom.xml

4 jobs for !49 with fix-version-os-core-common in 20 minutes and 10 seconds
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #357197
osdu-small allowed to fail

00:00:05

failed deprecated-pipeline-include #357196
allowed to fail

00:00:12

 
  Review
passed trigger-trusted-tests #357199
osdu-small

00:19:58

failed trigger-trusted-tests #357198
osdu-small

00:00:10

 
Name Stage Failure
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:6dbb9cc54074106d46d4ccb330f2a40a682d49dda5f4844962b7dce9fe44aaec for alpine:latest with digest alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f ...
$ 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/catalog_test_core/v2/swagger_client/models/__pycache__/
Removing testing/catalog_test_ibm/__pycache__/

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