set eks as deploy target

21 jobs for aws-eks in 22 minutes and 52 seconds
latest
Status Name Job ID Coverage
  Build
passed compile-and-unit-test #533368
osdu-medium

00:07:50

 
  Containerize
passed aws-containerize #533371
osdu-medium

00:02:29

passed azure_containerize #533372
osdu-medium

00:01:22

passed osdu-gcp-containerize-gcloud #533369

00:01:47

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

00:01:03

 
  Scan
passed bandit-sast #533376
osdu-medium

00:03:00

passed fossa-analyze #533373
osdu-medium

00:10:59

passed gemnasium-maven-dependency_scanning #533374
osdu-medium

00:05:50

passed gemnasium-python-dependency_scanning #533375
osdu-medium

00:04:02

passed license_scanning #533379
osdu-medium

00:03:30

passed semgrep-sast #533377
osdu-medium

00:02:30

passed spotbugs-sast #533378
osdu-large

00:12:33

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

00:01:00

passed azure_deploy #533384
osdu-medium

00:01:58

passed ibm-deploy #533382
osdu-medium

00:14:19

passed ibm-deploy-devpri #533383
osdu-medium

00:10:47

passed osdu-gcp-deploy #533380

00:01:04

 
  Integration
passed azure_test_py #533387
osdu-medium

00:02:54

passed ibm-test-py #533386

00:00:41

passed osdu-gcp-test-python #533385

00:00:54

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

00:00:36

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