Page MenuHomePhabricator

toolforge-jobs load should not abort running pods of unchanged tasks
Closed, ResolvedPublicBUG REPORT

Description

Any currently running pods are terminated when toolforge-jobs load command is run, even if no configuration related to them were changed.

Ideally, any running pods created by cronjobs should not be terminated if no change was made to that cronjob's config.

Also, I think running pods created by one-off jobs are probably better left as-is. To reduce some complexity, we could drop support for specifying one-off jobs in the YAML file, as this does not seem useful – only cronjobs and continuous jobs need to be supported.