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

UT Update

3 jobs for !112 with users/nikhil/ServiceBusEnabled in 25 minutes and 52 seconds (queued for 4 seconds)
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #574752
osdu-small allowed to fail

00:00:05

failed deprecated-gcp-pipeline #574751
allowed to fail

00:00:06

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

00:25:45

 
Name Stage Failure
failed
trigger-trusted-tests Review
Pipeline has been in state 'running' for 24.8 min, waiting for completion
Pipeline has been in state 'running' for 25.0 min, waiting for completion
Pipeline has been in state 'running' for 25.1 min, waiting for completion
Pipeline has been in state 'running' for 25.3 min, waiting for completion
Pipeline has been in state 'failed' for 7 sec, waiting for completion
Pipeline completed in state failed in 25.2 min
Pipeline status is not 'success', exiting with error status
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
deprecated-gcp-pipeline .Pre
Reinitialized existing Git repository in /builds/osdu/platform/system/register/.git/
Checking out bb440ef2 as refs/merge-requests/112/head...

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ echo "$DEPRECATED_MSG"
The integration test environment previously managed by the cloud-providers/gcp.yml is no longer supported. Consider removing it from your .gitlab-ci.yml
$ /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: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