KernelCI Dashboard Report - September 01 - September 15, 2025

Hello everyone,

We are back on track with our updates. Our database has been switched
from Google Cloud to Azure, but we are still in the moving process so
we haven’t disabled our use of GCloud yet. Apart from that, we have a
couple of improvements, some bugfixes and we are preparing some
changes to the database already. Here are the changes in the last
weeks:

## Docs
- The documents for onboarding and backend were updated in order to be
clearer. [1]

## Improvements
- The Hardware Details page now has a better way of selecting related
trees, also supporting deselecting all trees in order to pick a
specific one to inspect. [2]
- A test coverage badge was added to the backend readme, showing our
progress towards covering 100% of the functions and methods of the
backend. [3]
- A small UI fix to test, build and issue details pages, where long
titles wouldn’t wrap their text - Thanks to @khanheric2003. [4]

## Bug Fixes
- The cache for tree listing entries was not working correctly,
allowing old checkouts to be shown instead of the most recent one. [5]
- When selecting the specific commit for a tree related to a hardware
in the hardware details pages, some commits were shown repeatedly. [6]
- Some very specific trees had the “/” character on their branch and
weren’t parsing correctly. [7]
- In order to keep our security, we updated a lot of packages on our
frontend, this led to the search bar not working, which was quickly
fixed. [8]
- While fixing the search bar, another bug was fixed where links were
being nested inside other links. [9]
- With our move to a new database, our GitHub CI was missing data for
its integration tests, but it was fixed. [10]

## Future Changes
We have some tests to do with our database now that we can manage it
directly with Django, starting with some simple new fields which might
speed up some endpoints. We are also moving our CI to a local DB
approach, meaning that it will be faster and more reliable to test on
every PR, including ones coming from forks. And on that note, we also
expect to increase our backend test coverage progressively, in order
to have a solid codebase.


## References
[1] https://github.com/kernelci/dashboard/issues/1471
[2] https://github.com/kernelci/dashboard/issues/614
[3] https://github.com/kernelci/dashboard/issues/1443
[4] https://github.com/kernelci/dashboard/issues/1434
[5] https://github.com/kernelci/dashboard/issues/1457
[6] https://github.com/kernelci/dashboard/issues/1445
[7] https://github.com/kernelci/dashboard/issues/1468
[8] https://github.com/kernelci/dashboard/issues/1466
[9] https://github.com/kernelci/dashboard/issues/1470
[10] https://github.com/kernelci/dashboard/issues/1455