App Update

[DeepDiver1975]

ToDos:

• Add a background repair step which can be executed after upgrade during live operations
• Add a progress based feedback for longer running repair steps
• cleanup emitter vs. EventDispatcher (tech dept)
• enhance OCP\IRepairStep to hold feedback methods
• define backgroudjobs in info.xml @icewind1991 - does this somehow collide with your work?
• kill https://github.com/owncloud/core/blob/v9.0.1/lib/private/updater.php#L400

[icewind1991]

define backgroudjobs in info.xml @icewind1991 - does this somehow collide with your work?

The background jobs that would be defined in info.xml would be seperate from the job queue (job queue is for one-off async work)

[DeepDiver1975]

Just to be sure - we only have one queue and there is nothing going to change with this respect thinking about the executor mechanism you are building for 9.1

So no matter if the jobs are one shot of cron like they live in the same queue and will be equally executed amongst all job executors.

So as soon as a background job is defined in info.xml - we should throw it onto the job queue.

[icewind1991]

Background jobs (currently defined in update/install.php, to be moved to info.xml) execution will stay the same (cron.php) and is meant for periodic background jobs (news app sync, syncing of remote system address books, etc)

Job queue will get it's new fancy executor for 9.1 and is meant for one-off async work that is triggered by some action (trashbin expiry)

[DeepDiver1975]

Hmm .. I see no need to separate them in terms of who is executing them.

[DeepDiver1975]

Mainly done - remaining tasks can be ignored for now -> close

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.