Commit 28 Contents:

1-Unit Tests
3 jobs for !97 with users/nikhil/serviceBusSubscribers in 2 minutes and 27 seconds (queued for 4 seconds)
detached
Status Job ID Name Coverage
  .Pre
failed deprecated-aws-include #481421
osdu-small allowed to fail

00:00:05

failed deprecated-gcp-pipeline #481420
allowed to fail

00:00:09

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

00:02:17

 
Name Stage Failure
failed
trigger-trusted-tests Review
needs to launch a protected pipeline, which by convention is prefixed with 'trusted-'. Only maintainers
can create protected branches. If you are not a maintainer, please ask one to create a trusted branch for
you. They will need to inspect your branch for proper handling of secret variables before applying the trusted label.
If you are a maintainer, you need to push a branch named 'trusted-users/nikhil/serviceBusSubscribers', then re-run this pipeline.
----------------------------------------
If all else fails / something weird is going on, the logic in this script is maintained by:
David Diederich, @divido, d.diederich@opengroup.org
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 4667f8a2 as refs/merge-requests/97/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:d4ff818577bc193b309b355b02ebc9220427090057b54a59e73b79bdfe139b83 for alpine:latest with digest alpine@sha256:adab3844f497ab9171f070d4cae4114b5aec565ac772e2f2579405b78be67c96 ...
$ 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