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 file

6 jobs for !81 with core-lib-azure-update in 19 minutes and 28 seconds (queued for 1 second)
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #349549
osdu-small allowed to fail

00:00:05

failed deprecated-pipeline-include #349548
allowed to fail

00:00:12

failed deprecated-aws-include #349523
osdu-small allowed to fail

00:00:05

failed deprecated-pipeline-include #349522
allowed to fail

00:00:09

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

00:19:15

failed trigger-trusted-tests #349524
osdu-small

00:01:07

 
Name Stage Failure
failed
trigger-trusted-tests Review
Pipeline has been in state 'running' for 18.3 min, waiting for completion
Pipeline has been in state 'running' for 18.5 min, waiting for completion
Pipeline has been in state 'running' for 18.7 min, waiting for completion
Pipeline has been in state 'running' for 18.8 min, waiting for completion
Pipeline has been in state 'failed' for 6 sec, waiting for completion
Pipeline completed in state failed in 18.8 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
Removing testing/notification-test-gcp/target/
Removing testing/notification-test-ibm/target/

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: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