Skip to content

GitLab

Merge branch 'master' into dev

23 jobs for aws-integration in 36 minutes and 4 seconds (queued for 7 seconds)
01e516ff
2 related merge requests: !268 Update AWS Service Readme 2 related merge requests: !268 Update AWS Service Readme, !227 Use core lib aws version 0.12.0-SNAPSHOT
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #681053
osdu-small allowed to fail

00:00:07

 
  Build
passed compile-and-unit-test #681054
osdu-medium

00:11:52

passed osdu-gcp-helm-charts #681055
osdu-small

00:00:08

 
  Containerize
passed aws-containerize #681056
osdu-medium

00:02:59

passed azure_containerize #681057
osdu-medium

00:02:18

passed osdu-gcp-containerize-gitlab #681058
osdu-medium

00:01:32

 
  Scan
passed bandit-sast #681061
osdu-medium

00:08:18

passed fossa-analyze #681059
osdu-medium

00:14:43

passed gemnasium-maven-dependency_scanning #681060
osdu-medium

00:09:14

passed license_scanning #681064
osdu-medium

00:08:05

passed semgrep-sast #681062
osdu-medium

00:07:06

failed spotbugs-sast #681063
osdu-large allowed to fail

00:04:35

 
  Deploy
passed aws-update-eks #681065
osdu-medium

00:01:14

passed azure_deploy #681066
osdu-medium

00:04:01

passed ibm-deploy #681067
osdu-medium

00:07:45

passed osdu-gcp-deploy-configmap #681068

00:01:23

passed osdu-gcp-deploy-deployment #681069

00:00:25

 
  Integration
passed aws-test-java #681070
aws-internal-test

00:10:14

passed azure_test #681071
osdu-medium

00:17:27

passed ibm-test #681072
osdu-medium

00:15:33

failed osdu-gcp-test #681073
osdu-medium

00:03:44

 
  Attribution
failed fossa-check-notice #681074
osdu-small

00:01:24

passed fossa-report #681075
osdu-small

00:03:00

 
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=681074 responseStatus=201 Created token=zUFQmpBY
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
osdu-gcp-test Integration 
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
failed
spotbugs-sast Scan 
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
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