All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Fiege" <cfi@pengutronix.de>
To: Kevin Hilman <khilman@baylibre.com>, kernelci@groups.io
Subject: Re: RFC: dashboards, visualization and analytics for test results
Date: Mon, 07 Dec 2020 03:26:18 -0800	[thread overview]
Message-ID: <8699.1607340378432797045@groups.io> (raw)
In-Reply-To: <7hk0w2c4i3.fsf@baylibre.com>

Hey Kevin,

On Wed, Oct  7, 2020 at 10:47 AM, Kevin Hilman wrote:

>
> The KernelCI project is starting to look at what's next for dashboards,
> visualization and analytics for the various Linux focused testing
> projects.
> 
> (...)
> 
> So the next question is... how do we best use all of this data?
> 
> To that end, we're starting to collect a set of user stories to help us
> brainstorm a new design for web based dashboard and analytics, and we'd
> like to hear from you.

for us at Pengutronix Kernel-CI has always been a good way to present our
Kernel maintenance / development activities to our customers.

We are currently missing a few of the old views. I'll try to describe our
use-cases in some short user stories. Feel free to ask for more details.

A customer tries to evaluate whether to use  mainline Linux or a vendor kernel:
  - View of list of all hardware / SoC currently tested in all labs
  - View job history on all devices with a specific hardware / SoC
  - View statistics of failing / passing Tests over time for a specific hardware / SoC.

A member of sales department uses the contribution to Kernel-CI as an indication
for our effort to maintain systems for a long time.
  - View a list of hardware / SoC in a specific lab.
  - Send a link to said list to a costumer.
  - View the status of hardware in a specific lab:
    Are jobs scheduled for a specific hardware?
  - View the history of jobs for a specific lab.


Regards,
Chris

  parent reply	other threads:[~2020-12-07 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 17:47 RFC: dashboards, visualization and analytics for test results Kevin Hilman
2020-10-13 14:16 ` [cip-dev] FW: [Automated-testing] " Chris Paterson
2020-10-19 22:10 ` Nick Desaulniers
2020-10-20 21:39   ` Kevin Hilman
2020-10-21  6:39 ` Corentin Labbe
2020-10-21  6:39   ` LABBE Corentin
2020-12-07 11:26 ` Chris Fiege [this message]
2020-12-10 10:38 ` [Automated-testing] " Nikolai Kondrashov
2020-12-22 15:37 ` Chris Paterson
2020-12-22 15:37   ` Chris Paterson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8699.1607340378432797045@groups.io \
    --to=cfi@pengutronix.de \
    --cc=kernelci@groups.io \
    --cc=khilman@baylibre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.