From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: mahfouz.saif.elyazal@gmail.com, Nikolai Kondrashov <spbnick@gmail.com>
Cc: "kernelci@groups.io" <kernelci@groups.io>
Subject: Re: Notifications signup
Date: Fri, 15 Oct 2021 17:01:03 +0100 [thread overview]
Message-ID: <6697fbb3-59cf-a15e-84aa-9216c95306dd@collabora.com> (raw)
In-Reply-To: <CAJBmjuggPYrFPOt=+7Cc_QSpa+yhf77VWgLJRP2Eq=cfhzm66w@mail.gmail.com>
On 15/10/2021 16:39, Aya Mahfouz wrote:
> Hello Nikolai,
>
> I am looking for generic reports so any possible builds will be good.
The simplest way to get email notifications is to subscribe to
the kernelci-results mailing list:
https://groups.io/g/kernelci-results
It's quite high volume though, as you can see in the archive:
https://groups.io/g/kernelci-results/topics
Emails are also sent to kernel maintainers and specific mailing
lists with relevant reports. For example, you may subscribe to
the linux-next mailing list where reports from kernelci.org are
also sent but only for the linux-next git tree:
http://vger.kernel.org/vger-lists.html#linux-next
See also the archive on Lore:
https://lore.kernel.org/linux-next/
Best wishes,
Guillaume
> 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:01 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 [this message]
2021-10-15 18:04 ` Aya Mahfouz
2021-10-15 16:13 ` Nikolai Kondrashov
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=6697fbb3-59cf-a15e-84aa-9216c95306dd@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=kernelci@groups.io \
--cc=mahfouz.saif.elyazal@gmail.com \
--cc=spbnick@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