GitLab

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=681074 responseStatus=201 Created token=zUFQmpBY
Cleaning up file based variables
ERROR: Job failed: exit code 1

Uploading artifacts...
test-results.log: found 1 matching files and directories 
testing/indexer-test-gcp/target/*/TEST-*.xml: found 4 matching files and directories 
Uploading artifacts as "archive" to coordinator... ok  id=681073 responseStatus=201 Created token=vqMu1XpH
Uploading artifacts...
testing/indexer-test-gcp/target/*/TEST-*.xml: found 4 matching files and directories 
Uploading artifacts as "junit" to coordinator... ok  id=681073 responseStatus=201 Created token=vqMu1XpH
Cleaning up file based variables
ERROR: Job failed: exit code 1

Running after_script
Running after script...
$ tar -cC ~/.m2 repository | tar -xC $CI_PROJECT_DIR/.m2
Uploading artifacts for failed job
Uploading artifacts...
WARNING: gl-sast-report.json: no matching files    
ERROR: No files to upload                          
Cleaning up file based variables
ERROR: Job failed: exit code 1

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