Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-1855] Update mechanism : better feedback to user Created: 17/Nov/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 3.5
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MAGNOLIA-2067 Updater: feedback message implies job... Closed
relation
is related to MAGNOLIA-1667 Updatemech : the whole process should... Closed
is related to MAGNOLIA-1670 Updatemech : review exception handlin... Closed
is related to MAGNOLIA-2374 The title of the status page should b... Closed
is related to MAGNOLIA-2598 Module dependency issue should be dis... Closed
is related to MAGNOLIA-2109 Provide module status page Closed
is related to MAGNOLIA-2673 update: error message should print th... Closed
Template:
Date of First Response:

 Description   

At the moment, the only feedback the user gets, is the number of tasks that have been executed, along with the eventual info, warn or error messages tasks would yield, and that's refreshed every 3 seconds.
One of the frustrating things is that sometimes a save() operation (which happens after each successful module install/update) can take more than a few seconds, thus no progress is seen. Would be nice to send some feedback to the user about this, either through the form a message ("currently saving...") or some progress bar (eventhough afaik we have no way of knowing the actual progress of a save operation)

Another thing which we need to handle properly are failing tasks and exceptions. At the moment, the page keeps on refreshing itself, even if the actual update mechanism has been interrupted. This should also help with having tasks which fail on purpose, for instance if a restart is needed.



 Comments   
Comment by Magnolia International [ 25/Sep/08 ]

InstallContext or InstallStatus could have a method, callable by tasks, to give a message to the user about the current operation (useful for long running tasks for instance) - this message would be reset for every new task, and could also be used when saving workspaces.
An api with parameters à la slf4j would be very handy.

Comment by Magnolia International [ 11/Nov/10 ]

In addition to the above, or as a simpler approach, the InstallContext could keep a pointer to the currently executed task. "Saving" should also be a Task (if only a fake).
The UI could then simply print the "current task", thus keeping the user informed of what's going on.

Perhaps Task should have a read-only interface equivalent (TaskDescriptor), to avoid ambiguity.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:30:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.