Idea #2961
Updated by Peter Amstutz almost 10 years ago
The pipeline status page (and also individual job pages, they should share code as much as possible) should live update from event bus.
I think the way to do this is to use a client-side javascript template library. Based on my research, "jqote2":https://github.com/aefxx/jQote2 looks the most promising.
Benefits/rationale:
* Avoid displaying stale state, like a job that was submitted that starts running after 5 seconds, but you don't see that it started running until the page refreshes 30 seconds later, this makes the system seem slower than it actually is
* Synchronize job/pipeline log (already eventbus based) with other parts of the status display (so when the job log reports it ended, it doesn't continue to be shown as "running" until the next refresh)
* Closely tied to story #2882 (crunch stats) and #2883 (interactive job log browser)