From: Marcelo Robert Santos <marcelo.santos@profusion.mobi>
To: kernelci@lists.linux.dev
Cc: kernelci-webdashboard@groups.io
Subject: KernelCI Dashboard Report - July 24 - August 11, 2025
Date: Mon, 11 Aug 2025 15:13:15 -0300 [thread overview]
Message-ID: <CAMVAkEvB-HS79LZ82SHbagJ8tMURCvnHTShk0R1W2vd7X8ZEpQ@mail.gmail.com> (raw)
Hello everyone,
In the last weeks, we have been focused on the transition of KCIDB-ng
to the dashboard backend as an Azure Managed PostgreSQL. KCIDB-ng will
remain as the API for submitters to send their results in json files.
Production deployment will take a few weeks.
The preparation required some time from the Dashboard team to
understand the DB setup better and configure it well, alongside other
improvements that we worked on during this time.
## Database changes
- The new database was created and is managed by our backend with
Django ORM; its integration is being tested. [1]
- In order to move the database quickly, the new instance had its
foreign key constraints removed, making it more similar to kcidb. [2]
- Some schema changes were suggested, still needs some discussion as
to which will be implemented. [3]
- We are bringing the tool that parses submission data (the ingester)
into the dashboard repository, including some changes to allow for
insertion directly into the new database. [4]
## Improvements
- On the tree-report endpoint, it is now possible to specify the
interval to get checkouts and related tests. [5]
- The build, test and issue details pages were redesigned to have
better readability and organization. [6]
- The response from the issue extras endpoint was improved to be clearer. [7]
## Technical Debts
- Some tree endpoints had their code refined to allow for more
specific documentation. [8]
## Future changes
We plan to keep working on the transition to a new deployment for the
database, providing better performance for the queries and the
dashboard consequently. In parallel, some improvements will continue
to be made.
References
[1] https://github.com/kernelci/dashboard/issues/1332
[2] https://github.com/kernelci/dashboard/issues/1382
[3] https://github.com/kernelci/dashboard/issues/1334
[4] https://github.com/kernelci/dashboard/pull/1372
[5] https://github.com/kernelci/dashboard/pull/1374
[6] https://github.com/kernelci/dashboard/issues/1347
[7] https://github.com/kernelci/dashboard/issues/1335
[8] https://github.com/kernelci/dashboard/issues/1317
reply other threads:[~2025-08-11 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMVAkEvB-HS79LZ82SHbagJ8tMURCvnHTShk0R1W2vd7X8ZEpQ@mail.gmail.com \
--to=marcelo.santos@profusion.mobi \
--cc=kernelci-webdashboard@groups.io \
--cc=kernelci@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).