QA » openQA Project

https://github.com/os-autoinst/openQA/pull/1301

Have a look on the screenshots there to see the current status of the fullscreen view.
Next step will be to increase the size to make everything more visible and auto-update the page
without user interaction.

next steps:

• getting current status to a merge
• autorefresh (ajax)
• having a fullscreen view in the group overview (just showing the latest comment)
• alternative view-mods (having something like a graph instead of progressbars)
• filter for subgroups

• having a fullscreen view in the group overview:
  https://github.com/os-autoinst/openQA/pull/1435

• now working on ajax refresh and comments part

Current state of the ticket:

PR's open for:

• Full screen mode on group overview page
• Adjustable autorefresh rates for comments and build (currently only in full screen on group overview)

In progress:

• Possibility to limit comments to a certain amount

Further ideas:

• alternative view-mods (having something like a graph instead of progressbars)
• add auto-refresh to index page as well

When implementing an auto-reload feature for the dashboard we've noticed that there are a few details which should still be improved:

1. The auto-reload interval should be configurable via a from control (similar to the fullscreen mode).
2. The auto-reload on the group overview should use the same code as the index page. For that the group overview needs to be ported to use an AJAX query for loading the build results, too.
3. The time-ago rendering on the group overview is currently broken when enabling the auto-reload. (That is likely fixed when implementing 2. anyways.)

I found several additional problems

1. When you change from different intervals, all of them are added to the url
   .../group_overview/110?fullscreen=1&interval=30&interval=60
   .../group_overview/110?fullscreen=1&interval=30&interval=60&interval=90

2. When the autoupdate refresh the page is doing 2 refresh at the same time

About problem 2. The problem is here
https://github.com/os-autoinst/openQA/blob/d58e73ed410bf07e325d7318f0c12abb4dccf2ac/assets/javascripts/fullscreen.js#L37
$("#build-results").load(location.href + " #build-results");
$("#comments-preview").load(location.href + " #comments-preview");

The call adding #build-results is really not a different call than the second one, is the same, and both returns the progress and the comments, so in the screen is painting it twice.

Note, in ttp://127.0.0.1:9526/parent_group_overview allows to setup fullscreen but doesn't work

Initial PR to start solving things
https://github.com/os-autoinst/openQA/pull/3124

The best way to solve the repainting of the web should be have a screen part loading in base one parameter. Now I added a simple solution that repaints all

Autorefresh in index page
https://github.com/os-autoinst/openQA/pull/3141

This PR contains 3 commits

• First solves the problem
• Second, the autorefresh only works on fullscreen mode, and the filter is only selector when fullscreen mode is checked
• third, Fix the problem to open the filter panel when the page is in fullscreen mode

Hi ilausuch, the mentioned PR is merged and also deployed on osd now. What are your further plans for this?

Also one thing: Is there a reason why to use radio buttons for different refresh intervals instead of just a number field to select the value? As we have two number fields for "limit builds" I prefer to use the same for auto-refresh

cdywan wrote:

okurz wrote:

Also one thing: Is there a reason why to use radio buttons for different refresh intervals instead of just a number field to select the value? As we have two number fields for "limit builds" I prefer to use the same for auto-refresh

It looks like the radio buttons were already changed to links? Although the respective code change disagrees with what I'm seeing in production. I might be confused as to what's covered here?

Check yourself on https://openqa.opensuse.org/ , radio buttons with hardcoded choices whereas for "limit builds" we have number fields which I would prefer.

@ilausuch is it ok for you to do this change?

• there is configurable auto-refresh for "fullscreen" mode

So gh#os-autoinst/openQA#3141 seems to have implemented this?

Should it be considered DONE?

There was also the open question of the use of "number fields" to make the refresh options consistent with build limits.

I'd update the list of tasks, but it might be best for the OP (@asmorodskyi) to confirm.

PR for to change the automatic refresh selector
https://github.com/os-autoinst/openQA/pull/3368