Creating Release Commit

19 jobs for v0.12.0 in 29 minutes and 1 second (queued for 5 seconds)
latest
Status Name Job ID Coverage
  Build
passed compile-and-unit-test #685151
osdu-medium

00:09:36

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

00:00:09

 
  Containerize
passed aws-containerize #685154
osdu-medium

00:03:30

passed azure_containerize #685153
osdu-medium

00:02:43

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

00:02:23

 
  Scan
passed fossa-analyze #685156
osdu-medium

00:11:39

 
  Deploy
failed aws-update-eks #685730
osdu-medium

00:05:11

passed azure_deploy #685157
osdu-medium

00:02:41

passed ibm-deploy #685159
osdu-medium

00:03:16

passed osdu-gcp-deploy-configmap #685160

00:01:42

passed osdu-gcp-deploy-deployment #685161

00:01:27

failed aws-update-eks #685158
osdu-medium

00:05:46

 
  Integration
skipped aws-test-java #685163
osdu-medium
passed azure_test #685162
osdu-medium

00:08:38

passed ibm-test #685164
osdu-medium

00:03:43

passed osdu-gcp-test #685165
osdu-medium

00:03:01

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

00:02:31

passed fossa-report #685167
osdu-small

00:01:52

failed fossa-check-notice #685166
osdu-small

00:00:36

 
Name Stage Failure
failed
aws-update-eks Deploy
Added new context arn:aws:eks:us-east-2:198931730835:cluster/glosdu-green-main to /tmp/kubeconfig-18318.yaml
$ chmod 644 $KUBECONFIG
$ kubectl -n osdu-services rollout restart deployment/${AWS_EKS_DEPLOYMENT_NAME}
deployment.apps/os-entitlements restarted
$ kubectl -n osdu-services rollout status -w deployment/${AWS_EKS_DEPLOYMENT_NAME} --timeout=300s
Waiting for deployment "os-entitlements" rollout to finish: 1 old replicas are pending termination...
error: timed out waiting for the condition
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=685729 responseStatus=201 Created token=jBZXkg8_
Cleaning up file based variables
ERROR: Job failed: exit code 1