Skip to content

Conversation

@cromefire
Copy link
Contributor

@cromefire cromefire commented Dec 7, 2025

Description of the change

It would be good to allow setting activeDeadlineSeconds for the cronjob.

Benefits

That way you can configure a timeout for a job, so it can't get stuck.

Possible drawbacks

None ideally? It should not be active if it's not set.

Applicable issues

Additional information

Checklist

@cromefire cromefire force-pushed the add-activeDeadlineSeconds branch 4 times, most recently from 4813f1c to d50dd23 Compare December 7, 2025 00:59
@cromefire cromefire marked this pull request as ready for review December 7, 2025 01:02
Signed-off-by: Cromefire_ <cromefire.supernova559@passmail.com>
Signed-off-by: Cromefire_ <cromefire.supernova559@passmail.com>
@cromefire cromefire force-pushed the add-activeDeadlineSeconds branch from b4a6700 to 3eb110c Compare December 7, 2025 01:04
cromefire and others added 2 commits December 11, 2025 13:01
Co-authored-by: WrenIX <133280015+wrenix@users.noreply.github.com>
Signed-off-by: Cromefire_ <cromefire.supernova559@passmail.com>
Signed-off-by: Cromefire_ <cromefire.supernova559@passmail.com>
@wrenix wrenix enabled auto-merge (squash) December 11, 2025 12:04
Signed-off-by: WrenIX <133280015+wrenix@users.noreply.github.com>
@wrenix wrenix merged commit 7edffec into nextcloud:main Dec 13, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature: Add option for activeDeadlineSeconds

2 participants