Added partition variables

6 jobs for !84 with Add-PARTITION_API-variables in 24 minutes and 4 seconds (queued for 1 second)
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #355544
osdu-small allowed to fail

00:00:05

failed deprecated-pipeline-include #355543
allowed to fail

00:00:06

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

00:00:05

failed deprecated-pipeline-include #355511
allowed to fail

00:00:13

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

00:23:56

failed trigger-trusted-tests #355513
osdu-small

00:00:09

 
Name Stage Failure
failed
trigger-trusted-tests Review
Pipeline has been in state 'running' for 23.0 min, waiting for completion
Pipeline has been in state 'running' for 23.1 min, waiting for completion
Pipeline has been in state 'running' for 23.3 min, waiting for completion
Pipeline has been in state 'running' for 23.5 min, waiting for completion
Pipeline has been in state 'failed' for 9 sec, waiting for completion
Pipeline completed in state failed in 23.4 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 f0e22816 as refs/merge-requests/84/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: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