Re: kcidb vs KernelCI APIs

[Nikolai Kondrashov <spbnick@gmail.com>]

On 4/6/23 11:40, Nikolai Kondrashov wrote:
>> Looking at the retuned json, I see the "id" is 
>> "kernelci:staging.kernelci.org:642d52183d363bbbfd0b9bd3".
>>     a) Where did this id string come from, and how do I create such an ID if 
>> I want to submit my own test result using kcidb?
> 
> This string was generated by KernelCI Native backend when submitting its data 
> to KCIDB. I assume it took its internal test result ID 
> "642d52183d363bbbfd0b9bd3", added "staging.kernelci.org:" to indicate it's 
> coming from the staging instance, and to differentiate it from production 
> results, and then added "kernelci:" to indicate this test result is coming 
> from KernelCI itself, and to differentiate it from other CI systems.
> 
> The code doing that is likely here:
> https://github.com/kernelci/kernelci-backend/blob/main/app/utils/kcidb.py

To clarify further: the submitting CI system is solely responsible for keeping 
the IDs of the objects it sends to KCIDB unique among themselves. You can 
generate them however you wish, as long as they don't clash between 
themselves. E.g. you could concatenate the name of the host where the test 
executed with a timestamp, and the test process PID, to get a unique-enough 
ID. Or get them from the database you're storing your test results in, if you 
have any.

You're required to format them as a string and prepend them with "ti:" before 
submitting to KCIDB, though. The latter ensures that your IDs don't clash with 
IDs from others.

Nick