GONRG-1035

25 jobs for trusted-gcp-default-context-path in 20 minutes and 13 seconds (queued for 6 seconds)
Name Stage Failure
failed
fossa-check-notice Attribution
You can download the NOTICE file from this job's artifacts and directly commit it to the repository to resolve
this. Before doing so, review the differences to make sure that they make sense given the changes that you have
made. If they do not, reach out to a maintainer to help diagnose the issue.
Uploading artifacts for failed job
Uploading artifacts...
public: found 2 matching files and directories

Uploading artifacts as "archive" to coordinator... ok
id=531308 responseStatus=201 Created token=rsgZyBs8
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
azure_test Integration
Uploading artifacts...
WARNING: ./**/target/*.jar: no matching files
WARNING: ./**/maven-*-output.txt: no matching files
ERROR: No files to upload
Uploading artifacts...
testing/notification-test-azure/target/*/TEST-*.xml: found 2 matching files and directories

Uploading artifacts as "junit" to coordinator... ok
id=531304 responseStatus=201 Created token=Ku1qnEHj
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
ibm-deploy Deploy The deployment job is older than the previously succeeded deployment job, and therefore cannot be run
No job log
failed
deprecated-pipeline-include .Pre
Reinitialized existing Git repository in /builds/osdu/platform/system/notification/.git/
Checking out 8f6ebadf as trusted-gcp-default-context-path...

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:021b3423115ff662225e83d7e2606475217de7b55fde83ce3447a54019a77aa2 for alpine:latest with digest alpine@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae ...
$ 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