CI Build pod timeouts to be set based on timeout configured on the steps
complete
Q
Quaint Platypus
Currently the build pod that is spun up when running a CI stage using k8s infrastructure has a deadline of 24 hours. This can be noticed on the pod spec of the build pod spec.activeDeadlineSeconds. This makes it impossible for steps that have a timeout configured over 1 day. Ideally the build pod should respect the timeout configured on the steps and shall make running steps for longer durations (including days/weeks)
Log In
N
Nofar Bluestein
complete
Hey, this feature was delivered for K8S.
Please reach out to support to enable flag CI_ENABLE_LONG_TIMEOUTS if you require this capability.
Please refer to the documentation for more information: https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/ci-stage-settings/#stage-timeout
Regards,
Nofar Bluestein
CI product team
S
Silky Lobster
Hi, what is a status here?
This post was marked as
in progress
N
Nofar Bluestein
this fiscal quarter
N
Nofar Bluestein
next fiscal quarter
N
Nofar Bluestein
under review
Y
Yacht club Antelope
this makes long running database exports impossible if batch processes are expected to take longer than 24 hours (which is the case when exporting 2TB+ of data from DB to GCP buckets)
D
Different Leopard
Same problem here as well