From: "Nikolai Kondrashov" <spbnick@gmail.com>
To: Philip Li <philip.li@intel.com>
Cc: kernelci@groups.io,
Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com>,
lkp <lkp@intel.com>, "Xiong, Wei1X" <wei1x.xiong@intel.com>
Subject: Re: consult the KCIDB engagement from 0-Day CI
Date: Wed, 6 Jul 2022 15:33:14 +0300 [thread overview]
Message-ID: <8c723017-46e0-8e9d-6908-8becfd580ae3@gmail.com> (raw)
In-Reply-To: <YsTwYEHEX17FWHkR@rli9-dbox>
Hi Philip
>> Once you pick your "origin" ("intel", "0day", something else?), I will send
>> you submission credentials for our "playground" setup, in a private message.
>
> got it, i will pick "0dayci" as origin. Is this ok, or i need submit another
> mail to kernelci@groups.io by the guide?
Sure, no problem! I created the account and will send the credentials to you
in a bit. Please go ahead and use "0dayci" as your "origin".
Nick
On 7/6/22 05:16, Philip Li wrote:
> On Tue, Jul 05, 2022 at 06:06:09PM +0300, Nikolai Kondrashov wrote:
>> Hi Philip,
>>
>> On 7/5/22 08:37, Li, Philip wrote:
>>> Hi Nick, it has been for a while we haven't followed up with your last
>> contact, let me apologize for this.
>>
>> No problem, glad you found the time to write :)
>>
>>> I want to follow up to engage with kcidb to contribute the results from
>> 0-Day CI including kernel build and functional
>>> test results as we have bandwidth now. Is this ok? If yes, can you kindly
>> share us the process we need follow, such
>>> as account apply, test run, etc?
>>
>> Of course! You're more than welcome to join.
>>
>> Here's our official Submitter Guide:
>>
>> https://kernelci.org/docs/kcidb/submitter_guide/
>>
>> Once you pick your "origin" ("intel", "0day", something else?), I will send
>> you submission credentials for our "playground" setup, in a private message.
>
> got it, i will pick "0dayci" as origin. Is this ok, or i need submit another
> mail to kernelci@groups.io by the guide?
>
>>
>> You won't have to worry about breaking anything. You can send whatever you
>> want there to see how your data would look in our dashboard until you're
>> satisfied with what you're getting. Then we'll switch you to "production"
>> setup.
>>
>> Apart from the "playground" dashboard where your data will appear for now:
>>
>> https://kcidb.kernelci.org/?var-dataset=playground_kcidb_01
>>
>> You can also see examples of data coming from others at our "production"
>> dashboard:
>>
>> https://kcidb.kernelci.org/
>
> thanks for all detail info, we will follow up to try/learn.
>
>>
>> Send any questions you have!
>> Nick
>>
>> On 7/5/22 08:37, Li, Philip wrote:
>>> Hi Nick, it has been for a while we haven't followed up with your last contact, let me apologize for this.
>>>
>>> I want to follow up to engage with kcidb to contribute the results from 0-Day CI including kernel build and functional
>>> test results as we have bandwidth now. Is this ok? If yes, can you kindly share us the process we need follow, such
>>> as account apply, test run, etc?
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>>
>>
prev parent reply other threads:[~2022-07-06 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 5:37 consult the KCIDB engagement from 0-Day CI Li, Philip
2022-07-05 15:06 ` Nikolai Kondrashov
2022-07-06 2:16 ` Philip Li
2022-07-06 12:33 ` Nikolai Kondrashov [this message]
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=8c723017-46e0-8e9d-6908-8becfd580ae3@gmail.com \
--to=spbnick@gmail.com \
--cc=Nikolai.Kondrashov@redhat.com \
--cc=kernelci@groups.io \
--cc=lkp@intel.com \
--cc=philip.li@intel.com \
--cc=wei1x.xiong@intel.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