From: "Nikolai Kondrashov" <spbnick@gmail.com>
To: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
Cc: kernelci@groups.io
Subject: Re: Notifications signup
Date: Fri, 15 Oct 2021 19:13:02 +0300 [thread overview]
Message-ID: <49aa7dab-07eb-e218-4709-c28c0d0001aa@gmail.com> (raw)
In-Reply-To: <CAJBmjuggPYrFPOt=+7Cc_QSpa+yhf77VWgLJRP2Eq=cfhzm66w@mail.gmail.com>
Hi Aya,
On 10/15/21 6:39 PM, Aya Mahfouz wrote:
> I am looking for generic reports so any possible builds will be good.
If the maillists Guillaume suggest don't work for you, I'll be able to
subscribe you to notification emails with the next release of KCIDB, coming
this Autumn. Those would be human-targeted, though.
An alternative to get *structured* KCIDB data could be to mine our dataset
directly with SQL. See examples in the slides for a presentation I did,
starting from this one:
https://docs.google.com/presentation/d/1ZrU0z1LvQYYoLOb9vmXUH7aZ9jSFviaenZRcYtEWqVg/edit#slide=id.gbcaa06c4d2_0_44
Links at the bottom of slides should work. Beside the SQL console, there are
of course APIs available for querying.
Another alternative is to subscribe to our submission message queue to receive
build (as well as test) results in (relative) real time, as they come in. We
have a formal, documented schema for those JSON messages.
You can check out what data is available in KCIDB on the dashboard:
https://kcidb.kernelci.org/
Nick
On 10/15/21 6:39 PM, Aya Mahfouz wrote:
> Hello Nikolai,
>
> I am looking for generic reports so any possible builds will be good.
>
> Thanks,
>
> Kind Regards,
> Aya Saif El-yazal Mahfouz
>
>
> On Fri, Oct 15, 2021 at 11:16 AM Nikolai Kondrashov <spbnick@gmail.com
> <mailto:spbnick@gmail.com>> wrote:
>
> Hi Aya,
>
> On 10/14/21 9:28 PM, Aya Mahfouz wrote:
> > Hello,
> >
> > I would like to sign up for receiving notifications of incoming build
> > results. In addition, I would like to ask if there is an API for the
> public to
> > fetch the build results in json format.
>
> Do you want to receive native KernelCI build result notifications, or the
> KCIDB build notifications, which include build results from multiple other CI
> systems?
>
> Which criteria do you want the notifications to be filtered by? Particular
> tree, repo, architecture, and so on?
>
> Nick
>
> On 10/14/21 9:28 PM, Aya Mahfouz wrote:
> > Hello,
> >
> > I would like to sign up for receiving notifications of incoming build
> > results. In addition, I would like to ask if there is an API for the
> public to
> > fetch the build results in json format.
> >
> > Thanks,
> >
> > Kind Regards,
> > Aya Saif El-yazal Mahfouz
> >
>
next prev parent reply other threads:[~2021-10-15 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 18:28 Notifications signup Aya Mahfouz
2021-10-15 9:16 ` Nikolai Kondrashov
2021-10-15 15:39 ` Aya Mahfouz
2021-10-15 16:01 ` Guillaume Tucker
2021-10-15 18:04 ` Aya Mahfouz
2021-10-15 16:13 ` Nikolai Kondrashov [this message]
2021-10-15 18:18 ` Aya Mahfouz
2021-10-16 8:54 ` Nikolai Kondrashov
2021-10-16 19:40 ` Aya Mahfouz
2021-10-18 9:25 ` Nikolai Kondrashov
[not found] ` <16AF15C1A99967B5.13161@groups.io>
2021-10-18 9:27 ` Nikolai Kondrashov
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=49aa7dab-07eb-e218-4709-c28c0d0001aa@gmail.com \
--to=spbnick@gmail.com \
--cc=kernelci@groups.io \
--cc=mahfouz.saif.elyazal@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox