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

use aws custom image for bootstrap

29 jobs for aws-integration in 69 minutes and 40 seconds (queued for 9 seconds)
latest
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #534202
osdu-small allowed to fail

00:00:25

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

00:08:24

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

00:01:42

 
  Containerize
passed aws-containerize #534205
osdu-medium

00:01:48

passed azure_containerize #534206
osdu-medium

00:02:38

passed osdu-gcp-containerize-gcloud #534207

00:02:10

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

00:02:08

 
  Scan
passed bandit-sast #534212
osdu-medium

00:05:33

passed fossa-analyze #534209
osdu-medium

00:16:05

passed gemnasium-maven-dependency_scanning #534210
osdu-medium

00:11:17

passed gemnasium-python-dependency_scanning #534211
osdu-medium

00:06:59

passed license_scanning #534215
osdu-medium

00:06:43

passed semgrep-sast #534213
osdu-medium

00:06:31

passed spotbugs-sast #534214
osdu-large

00:19:32

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

00:02:24

passed azure_deploy #534219
osdu-medium

00:02:08

passed ibm-deploy #534217
osdu-medium

00:17:40

passed ibm-deploy-devpri #534218
osdu-medium

00:18:52

passed osdu-gcp-deploy #534220

00:00:57

 
  Bootstrap
passed aws_bootstrap #534222
osdu-medium

00:02:47

passed azure_bootstrap #534221

00:03:52

passed ibm_bootstrap #534223

00:04:18

passed osdu_gcp_bootstrap #534224

00:05:43

 
  Integration
passed aws-test-java #534225
osdu-medium

00:05:55

failed azure_test #534227
osdu-medium

00:36:36

passed ibm-test #534226
osdu-medium

00:11:10

failed osdu-gcp-test #534228
osdu-medium

00:51:41

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

00:02:22

passed fossa-report #534230
osdu-small

00:02:20

 
Name Stage Failure
failed
osdu-gcp-test Integration
Uploading artifacts...
test-results.log: found 1 matching files and directories

testing/schema-test-core/target/*/TEST-*.xml: found 3 matching files and directories

Uploading artifacts as "archive" to coordinator... ok
id=534228 responseStatus=201 Created token=Lvx9ceRS
Uploading artifacts...
testing/schema-test-core/target/*/TEST-*.xml: found 3 matching files and directories

Uploading artifacts as "junit" to coordinator... ok
id=534228 responseStatus=201 Created token=Lvx9ceRS
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
azure_test Integration
Uploading artifacts...
./**/target/*.jar: found 1 matching files and directories

WARNING: ./**/maven-*-output.txt: no matching files
Uploading artifacts as "archive" to coordinator... ok
id=534227 responseStatus=201 Created token=b6eHWh1y
Uploading artifacts...
testing/schema-test-core/target/*/TEST-*.xml: found 3 matching files and directories

Uploading artifacts as "junit" to coordinator... ok
id=534227 responseStatus=201 Created token=b6eHWh1y
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=534229 responseStatus=201 Created token=HFAVL3CW
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