Open jospoortvliet opened 3 years ago
(pls correct if this isn't a starter issue, but I guess that just offering to run cron wouldn't be magically hard)
Related: https://github.com/nextcloud/updater/issues/321 -> execute the recommendations. Not as crucial, but certainly nice.
Yep makes sense 👍
A note in the docs was recently added for this: nextcloud/documentation#10636
Triggering a cron run once is easy enough (if that's all that is indeed needed; docs currently say run 2-3 times) but...
What jobs are we concerned with specifically here? I only see these referenced by the Updater:
Otherwise most things are in the Repair steps that get ran at the end automatically already:
And the core migrations that also get ran:
It appears what is most important is that the jobs get installed (which they always do before the update/upgrade finishes). Is it really important that they run before the next update/upgrade? None of the jobs look all that critical (though I suppose there could be differences between major version hops that don't appear in the next major, or in some apps, or something).
Maybe I'm overlooking something because this is specific to older Server versions?
@SystemKeeper You recently looked a bit at this for the doc addition; any idea what jobs are of concern during the update/upgrade cycle?
Related:
nextcloud/server#28508 nextcloud/server#45513 nextcloud/server#24777
After an upgrade, cron has to run at least once to finish some things that might take longer. When you're upgrading quickly through major releases (say you go from 12 to 20) you risk problems if you don't run cron in between, but most admins won't know this.
We should warn, or better, offer to run cron after the upgrade is complete.