KernelCI Dashboard Report - July 9 - July 23, 2025

Marcelo Robert Santos <[email protected]> Wed, 23 Jul 2025 09:20:46 -0300
Newsgroups dev.linux.lists.kernelci
Message-ID <CAMVAkEt=6dCgg2TtV_kZ-Yi_H1MTS5UWEW+5Sr4FCocUhzWcWA@mail.gmail.com>
Hello everyone,

Here are the changes in the last sprint:


## Database changes

- A new dashboard database is being created to replace the current
PostgreSQL deployment from KCIDB. The new database will be used to try
out a better organization and schema for the dashboard. Meanwhile,
*kcidb will continue to be used with no changes, and no data will be
lost*. [1]
- In order to have a smoother transition, the models in the dashboard
were synced to kcidb. [2]
- The test/build log excerpt is already supporting the new format of a
link to the stored excerpt. [3]


## Improvements

- On tree endpoints, it is now possible to use git commit tags instead
of git commit hashes. In the frontend they will respond correctly but
it still defaults to the commit hash. [4]
- The origins endpoint now has a time limit, hiding origins without
any checkouts in the past 30 days, a number which can be changed with
query parameters. [5]
- Kci-summary endpoint was renamed to tree-report. [6]


## Bugfixes

- The breadcrumb component was breaking with the new tree details url,
now it will maintain the shorter url between pages. [7]
- The path parameter in the kci-summary (now tree-report) endpoint was
not parsing strings properly. [8]
- The use of a different query in tree-report was allowing for an exit
without returning any error message. [9]
- Tree listing and issue listing endpoints weren’t grabbing the
default interval_in_days. [10]


## Notifications

- Added test_report action for manual test reporting [11]
- Replaced gmail api with SMTP for email sending [12]
Other improvements in the email structure


## Future changes

As we move forward, we plan on focusing a bit more on the database
changes, providing more solid and faster results to all users. This
will require a careful study of the technologies and interactions
involved, but will lead to a better experience in the dashboard.

References
[1] https://github.com/kernelci/dashboard/issues/1332
[2] https://github.com/kernelci/dashboard/issues/1342
[3] https://github.com/kernelci/dashboard/issues/1331
[4] https://github.com/kernelci/dashboard/issues/1320
[5] https://github.com/kernelci/dashboard/issues/1322
[6] https://github.com/kernelci/dashboard/issues/1344
[7] https://github.com/kernelci/dashboard/issues/1314
[8] https://github.com/kernelci/dashboard/issues/1329
[9] https://github.com/kernelci/dashboard/issues/1328
[10] https://github.com/kernelci/dashboard/issues/1340
[11] https://github.com/kernelci/dashboard/pull/1354
[12] https://github.com/kernelci/dashboard/pull/1348