RE: Request KCIDB Submit Token for Test Result Submission

Hi KernelCI team,

Thanks again for your earlier guidance. We’ve set up an event listener, integrated it with our system, and are periodically fetching events, downloading images, and triggering boot tests.

I have a few follow-up questions regarding result submission:

1. Artifact uploads (logs)
Is there a supported way to push boot logs directly to files.kernelci.org (e.g., via API)? I’ve noticed that uploaded JSON files always include a log_excerpt URL.
If not, could you recommend the preferred upload location, along with any directory structure, naming, or metadata conventions we should follow?

2. Submitter name
Can we choose our own submitter name (e.g., aspeed), or does it need to be pre-registered? Are there any format constraints we should be aware of?

3. Platform (Hardware) registration
Does the test platform (hardware) need to be pre-registered in KernelCI, or can it simply be included in the JSON (e.g., under misc as described https://docs.kernelci.org/components/kcidb/submitter_guide/#extra-data)?
If there is an example JSON for this, could you please share it?

Thanks again for your support!

Best regards,
Liping Shen
ASPEED Technology
[email protected]

-----Original Message-----
From: Gustavo Padovan <[email protected]> 
Sent: Thursday, July 3, 2025 8:12 PM
To: Liping Shen <[email protected]>
Cc: [email protected]; Ryan Chen <[email protected]>; Denys Fedoryshchenko <[email protected]>
Subject: Re: Request KCIDB Submit Token for Test Result Submission

Hiy Liping,

It is great to hear of your interest to test with KernelCI.

I'll answer you inline.


---- On Thu, 03 Jul 2025 03:27:08 -0300 Liping Shen <[email protected]> wrote ---

 > Hi KernelCI team,
 > I’m Liping from ASPEED Technology. We’d like to request a KCIDB submit token so we can submit our test results.
 > Our setup is more of a legacy system, and we’d like to connect to KCIDB using a polling + submit approach.
 > Our plan is to:
 >
 > 1. Poll for KernelCI-built images

Yes.  You can take this example code to listen to the events

https://github.com/kernelci/kernelci-pipeline/blob/main/tools/example_api_events.py

 >
 > 2. Run tests (boot, etc.) on ASPEED physical hardware  >  > 3. Submit test results to KCIDB using the kcidb-submit tool. The attachment contains the report data from our boot tests using KernelCI-built images.

Denys will get you a token to our staging KCIDB-ng instance. We are in the middle of a transition to our new KCIDB infra, so the docs will be a bit influx for the coming weeks. We are sorry about that.

 >
 > We’ll start in the Playground environment and move to Production once everything’s validated.
 > We would appreciate any advice from you.
 >  Let us know what information you need to move forward, and we’re happy to provide details about  test flow.Thanks a lot for your help!

Great. If you want to join our chat at Discord to ask questions, you are more than welcome: https://discord.gg/KWbrbWEyqb

Let me know how it goes, I'd be happy to review what you do and help you polish the data submission to KCIDB.

Best,

- Gus