Skip to content

GitLab

Merge remote-tracking branch 'upstream/master' into aws-eks

26 jobs for aws-eks in 36 minutes and 20 seconds (queued for 10 seconds)
cacc764b
1 related merge request: !147 Deploy to EKS
Name Stage Failure
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/legal-test-azure/target/*/TEST-*.xml: found 9 matching files and directories 
Uploading artifacts as "junit" to coordinator... ok  id=533473 responseStatus=201 Created token=7J6C12Jx
Cleaning up file based variables
ERROR: Job failed: exit code 1
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=533475 responseStatus=201 Created token=fvNMwzkq
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
aws-test-java Integration 
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
**** Showing the last 200 lines of the failed build (above). See Job artifacts for full log details *****

Uploading artifacts for failed job
Uploading artifacts...
testing/legal-test-aws: found 80 matching files and directories 
Uploading artifacts as "archive" to coordinator... ok  id=533471 responseStatus=201 Created token=xcb6G_Wp
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
ibm-deploy Deploy 
NAME    TYPE     FROM     LATEST
legal   Source   Binary   120
$ oc start-build $CI_PROJECT_NAME --from-dir=. --follow
Uploading directory "." as binary input for the build ...
............................................................
Uploading finished
Error from server (BadRequest): unable to wait for build legal-121 to run: timed out waiting for the condition
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
ibm-deploy-devpri Deploy 
NAME    TYPE     FROM     LATEST
legal   Source   Binary   19
$ oc start-build $CI_PROJECT_NAME --from-dir=. --follow
Uploading directory "." as binary input for the build ...
............................................................
Uploading finished
Error from server (BadRequest): unable to wait for build legal-20 to run: timed out waiting for the condition
Cleaning up file based variables
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
failed
deprecated-gcp-pipeline .Pre 
Reinitialized existing Git repository in /builds/osdu/platform/security-and-compliance/legal/.git/
Checking out cacc764b as aws-eks...

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-pipeline-include .Pre 
Removing testing/legal-test-ibm/target/
Removing testing/maven-build-output.txt

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