unique ID for Reported-by tag

[khilman]

When reporting bisection bugs/regressions, we should add a unique ID to the Reported-by tag so that issues raised can be tracked.

e.g.

Reported-by: kernelCI bot bot@kernelci.org #

This would allow us to check/verify when reported fixes have made it upstream.

[sladyn98]

@gctucker I could get started with this, could you provide some insight on how to get started.

[gctucker]

@sladyn98 Sure, first you probably need to have a local setup with a kernelci-backend instance to be able to work on the code. Please ask on Freenode #kernelci IRC channel for some instructions, it's typically deployed with Ansible but there's now also a Docker image you should be able to use.

Each bisection has an entry in the kernelci-backend's Mongo DB. There is already a unique ID for each entry automatically created by Mongo DB so we could use that. The risk is that it's local to the database, if there are other instances or if the data gets reconstructed somehow it may cause some collisions. So for including in emails and long-term archiving, we probably need to create a UUID field.

Also, going forward we should be tracking every regression or "issue" automatically found by KernelCI. So we may actually need to create a new type of entry in the database for this purpose. The schema would need to be revisited a bit, between test cases, test groups, regressions, bisections and issues.