STA 2025 Milestone 2+3: Update dashboard, Bugzilla stats, bug triage page and autobuilder issues page#11
STA 2025 Milestone 2+3: Update dashboard, Bugzilla stats, bug triage page and autobuilder issues page#11
Conversation
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Removed all Google Chart and Material libraries, replaced with Pico.css, Apache eCharts and modern web technologies Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Replaced Google Material libraries with Pico.css, updated table sorting library. Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Uses Pico.css and Apache eCharts, reworked rendering: abint.py now generates a JSON file that is consumed by a static index.html. Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
26a5f90 to
5d30927
Compare
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
6005085 to
fc06f3d
Compare
|
Hello @rossburton! I’ve fixed All The Things™. The abint page has received all five fixes you asked for, including the old opacity behaviour :) The table is now fully visible down to 640px width, and below that overflows and becomes scrollable. The bug triage page has also received all fixes. It’s been tidied up a lot, displaying much more information in the same space. In addition to your requests, I’ve also sorted out the header, which is now fixed to the top on small screens, for easier access to the navigation. Super strange that the column sorting arrows worked for you on the bug triage page, but not on the abint page, they were done in the same way. I’ve changed them to svg icons though, just in case. |
|
On the bug triage page:
|
|
On the abint page, the colouring logic is still a bit funky. I wasn't precise about the existing logic: 30% overlay per occurrence and the alphas interact, so once is 30% blue, twice is ~50%, three times is ~70%. The new logic you've implemented is 30% per instance, so twice is 60% and three times is 90%. This means anything over 3 instances a week is basically solid blue. However, we don't need to replicate that logic fully as it's just how my hack implementation ended up. A simple page-wide 1 occurrence=30%, 10+ occurrences=100% with a linear progression between them should work. |
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
Signed-off-by: Alex Feyerke <alex@neighbourhood.ie>
|
Alright, that should do it :) |




This PR constitutes the entirety of the work on the STA Milestones 2 and 3 for Yocto in 2025: Improved design and unified website pages, concerning:
In general, the work consisted of:
A detailed description follows, with screenshots for each.
Work items:
1. Update Dashboard
Live: https://dashboard.yoctoproject.org/
Source:
yocto-autobuilder-helper/scripts/dashboard/index.htmlChanges:
2. Update Bugzilla Stats
Live: https://wiki.yoctoproject.org/charts/combo.html
Source:
yocto-autobuilder-helper/scripts/dashboard/bugzilla_stats.htmlChanges:
https://wiki.yoctoproject.org/charts/importance-weekly.txtetc. once deployed3. Bug Triage Page
Live: https://dashboard.yoctoproject.org/bugtriage/
Source:
yocto-autobuilder-helper/scripts/dashboard/bugtriage/index.htmlChanges:
4. Autobuilder Issue Summary
Live: https://valkyrie.yocto.io/pub/non-release/abint/
Source:
yocto-autobuilder-helper/scripts/abintChanges:
abint.pyto generate abugs.jsonfile with the bug data, it no longer outputs any html. The JSON is consumed by JS a staticindex.htmlfile.bugs.jsonand the/resourcesfolder get deployed correctly in production, they should land right next to the built html file (See changes in/scripts/run-abint)JSONbug data, using Pico.css for consistent styling and Apache eCharts to render the single-axis heatmaps./resources(css, eCharts library etc).