There is a security vulnerability in SSH key-generation using GitKraken < v8.0.1. If you used this tool to create SSH keys, please update GitKraken and regenerate. If you need help with this, contact forum-support@opengroup.org

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

25 jobs for aws-integration in 52 minutes and 4 seconds (queued for 7 seconds)
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #537865
osdu-small allowed to fail

00:01:55

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

00:10:07

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

00:00:17

 
  Containerize
passed aws-containerize #537868
osdu-medium

00:02:05

passed azure_containerize #537869
osdu-medium

00:02:04

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

00:01:22

 
  Scan
passed bandit-sast #537873
osdu-medium

00:09:18

passed fossa-analyze #537871
osdu-medium

00:14:51

passed gemnasium-maven-dependency_scanning #537872
osdu-medium

00:12:45

passed license_scanning #537877
osdu-medium

00:11:04

passed security-code-scan-sast #537874
osdu-medium

00:08:55

passed semgrep-sast #537875
osdu-medium

00:08:46

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

00:06:04

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

00:01:22

passed azure_deploy #537881
osdu-medium

00:13:33

passed ibm-deploy #537879
osdu-medium

00:22:11

passed ibm-deploy-devpri #537880
osdu-medium

00:13:45

passed osdu-gcp-deploy-configmap #537882

00:01:28

passed osdu-gcp-deploy-deployment #537883

00:00:34

 
  Integration
failed aws-test-java #537884
aws-internal-test

00:03:14

passed azure_test #537886
osdu-medium

00:16:19

passed ibm-test #537885
osdu-medium

00:14:34

passed osdu-gcp-test #537887
osdu-medium

00:12:28

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

00:03:19

passed fossa-report #537889
osdu-small

00:02:49

 
Name Stage Failure
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 *****

Running after_script
Uploading artifacts for failed job
Uploading artifacts...
testing/integration-tests/search-test-aws: found 73 matching files

Uploading artifacts to coordinator... ok
id=537884 responseStatus=201 Created token=uGtPFsgh
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=537888 responseStatus=201 Created token=bECCPy8D
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: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