HorizonStackSoftware/optima
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

fix(ci): increase dalpuri sync timeout from 30min to 2h

Browse Source 
Full initial sync has 500k+ rows across all tables and exceeded the
30-minute activeDeadlineSeconds. Bump both the k8s job deadline and
the kubectl wait timeout to 7200s (2 hours).
This commit is contained in:
Jackson Roberts
2026-04-08 21:19:43 +00:00
parent a106bb15a8
commit a3bfe9f374
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/deploy.yaml
+2 -2
View File
@@ -318,9 +318,9 @@ jobs:
TAG=${{ github.event.release.tag_name }} TAG=${{ github.event.release.tag_name }}
JOB="job/dalpuri-sync-${TAG}" JOB="job/dalpuri-sync-${TAG}"
kubectl wait --for=condition=complete --timeout=1800s -n optima "$JOB" & kubectl wait --for=condition=complete --timeout=7200s -n optima "$JOB" &
WAIT_COMPLETE=$! WAIT_COMPLETE=$!
kubectl wait --for=condition=failed --timeout=1800s -n optima "$JOB" & kubectl wait --for=condition=failed --timeout=7200s -n optima "$JOB" &
WAIT_FAILED=$! WAIT_FAILED=$!
wait -n $WAIT_COMPLETE $WAIT_FAILED wait -n $WAIT_COMPLETE $WAIT_FAILED
dalpuri/kubernetes/sync-job.yaml
+1 -1
View File
@@ -8,7 +8,7 @@ metadata:
spec: spec:
backoffLimit: 0 backoffLimit: 0
ttlSecondsAfterFinished: 86400 ttlSecondsAfterFinished: 86400
activeDeadlineSeconds: 1800 activeDeadlineSeconds: 7200
template: template:
metadata: metadata:
labels: labels: