astonishing-tomato-18259
06/13/2023, 12:02 PMjobs
are not managed by garden. A job can create one more more pods and continue to retry execution of the Pods until a specified number of them successfully terminate or the desired number of pods can't be started after specified retries.
Making garden wait for the completion of jobs doesn't seem ideal as the nature of job could range from short-lived, parallel, or sequential batch tasks within the cluster to tasks like background data processing etc.
@swift-garage-61180 and I discussed this already and would argue that if you need to wait for a deploy in your pipeline, job
isn't the right resource and shouldn't be used. exec
or pod
would be more suitable.
@icy-furniture-17516 As you originally reported the issue, what do you think?icy-furniture-17516
06/13/2023, 12:30 PMfreezing-pharmacist-34446
06/13/2023, 1:19 PMicy-furniture-17516
06/13/2023, 2:13 PM--wait-for-jobs if set and --wait enabled, will wait until all Jobs have been completed before marking the release as successful. It will wait for as long as --timeout
freezing-pharmacist-34446
06/13/2023, 2:58 PMicy-furniture-17516
06/13/2023, 3:50 PMastonishing-tomato-18259
06/13/2023, 3:54 PMrun
action type and give feedback. The reason for starting this thread was mainly to discuss this instead of marking the issue as resolved, or introducing the default behavior of waiting for jobs as that would affect other users.icy-furniture-17516
06/13/2023, 3:56 PMastonishing-tomato-18259
06/30/2023, 4:27 PMicy-furniture-17516
06/30/2023, 4:28 PM