initial commit

3 jobs for !136 with Azure/add-micrometer-prometheus in 2 minutes and 28 seconds (queued for 6 seconds)
detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #676924
osdu-small allowed to fail

00:01:36

failed deprecated-pipeline-include #676923
allowed to fail

00:02:15

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

00:00:11

 
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-Azure/add-micrometer-prometheus', 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-pipeline-include .Pre
Pulling docker image alpine ...
Using docker image sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab for alpine ...
Preparing environment
Running on runner-u67ei7fk-project-143-concurrent-0 via f27fbf3426b2...
Getting source from Git repository
Fetching changes with git depth set to 50...
Reinitialized existing Git repository in /builds/osdu/platform/system/notification/.git/
fatal: unable to access 'https://community.opengroup.org/osdu/platform/system/notification.git/': Failed to connect to community.opengroup.org port 443: Operation timed out
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