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

Updated NOTICE

4 jobs for !101 with version-endpoint in 23 minutes and 20 seconds (queued for 3 seconds)
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #509125
osdu-small allowed to fail

00:00:05

failed deprecated-pipeline-include #509124
allowed to fail

00:00:12

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

00:23:07

failed trigger-trusted-tests #509126
osdu-small

00:02:09

 
Name Stage Failure
failed
deprecated-pipeline-include .Pre
Reinitialized existing Git repository in /builds/osdu/platform/system/notification/.git/
Checking out 7700fdbd as refs/merge-requests/101/head...

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
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:021b3423115ff662225e83d7e2606475217de7b55fde83ce3447a54019a77aa2 for alpine:latest with digest alpine@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae ...
$ 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