Hi team,
I would like to open discussion on topic "Task Result Dashboards". I'm posting
here in order to avoid long of the grid discussions we had last time regarding
the docker testing stuff.
There is a tracking ticket in phab [1] that links to tflink's initial ideas [2].
* What is the motivation, what do we want to achieve with such dashboards and
who is the 'non-techincal audience'?
* Runnable once a day or once per hour at minimum; does this imply static
periodically refreshed page? If so, what is the motivation for
static website?
After brief discussion with jskladan, I understand that resultsDB would be
able to handle requests from dynamic page.
* I'm not sure what exactly is meant by 'item tag' in the examples section.
* Would the YAML configuration look something like this:
url: link.to.resultsdbapi.org
overview:
- testplan:
- name: LAMP
- items:
- mariadb
- httpd
- tasks:
- and:
- rpmlint
- depcheck
- or:
- foo
- bar
Is there going to be any additional grouping (for example, based on arch) or
some kind of more precise outcome aggregation (only warn if part of testplan
is failing, etc.)
* Are we going to generate the dashbord for the latest results only, or/and
some kind of summary over given period in history?
* How are Task dasboards related to Static dashboards [3]
[1] https://phab.qa.fedoraproject.org/T725
[2] https://bitbucket.org/tflink/taskdash
[3] https://phab.qa.fedoraproject.org/T738
_______________________________________________
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
