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

master merge

3 jobs for !88 with add_node_selector in 21 minutes and 7 seconds (queued for 6 seconds)
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #533746
osdu-small allowed to fail

00:00:06

failed deprecated-pipeline-include #533745
allowed to fail

00:00:20

 
  Review
failed trigger-trusted-tests #533747
osdu-small

00:20:45

 
Name Stage Failure
failed
trigger-trusted-tests Review
Pipeline has been in state 'running' for 19.6 min, waiting for completion
Pipeline has been in state 'running' for 19.8 min, waiting for completion
Pipeline has been in state 'running' for 20.0 min, waiting for completion
Pipeline has been in state 'running' for 20.2 min, waiting for completion
Pipeline has been in state 'failed' for 6 sec, waiting for completion
Pipeline completed in state failed in 20.1 min
Pipeline status is not 'success', exiting with error status
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 86f5bb92 as refs/merge-requests/88/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