From: Guillaume Tucker <gtucker@gtucker.io>
To: kernelci@lists.linux.dev, automated-testing@lists.yoctoproject.org
Cc: kernelci-tsc@groups.io, kernelci-members@groups.io,
Shuah Khan <skhan@linuxfoundation.org>
Subject: [RFC] KernelCI Travel Guide 2024 LF webinar - 21st March
Date: Sun, 3 Mar 2024 23:35:17 +0100 [thread overview]
Message-ID: <71f59a56-aef3-4bae-867b-769a0cdd1c1b@gtucker.io> (raw)
Hello,
On 21st March I'll be giving an online talk about KernelCI as
part of the LF Live Mentorship series of webinars:
https://www.linuxfoundation.org/webinars/kernelci-travel-guide-2024
While this is not something I'm doing on behalf of the KernelCI
project itself but as an individual, it seemed appropriate to me
to bring it up here and collect any potential feedback from the
community. Is there anything in particular you think should be
covered? Please see the current outline below, it's not set in
stone and there's still some room for additional topics.
In particular, I was wondering whether there was an update on the
new API roadmap which was meant to reach its main milestone
today (4th March) with the production switchover. On a related
topic, the UX Analysis work is currently on-going but I haven't
seen any public update on this either. Generally speaking, if
there's anything that seems important to add regarding all the
recent developments then please let me know. This is more about
the last part with the 2024 horizon.
Thanks,
Guillaume
----------------------------------------------------------------
Outline for "KernelCI: Travel Guide 2024"
* Part 1: History
(10 years in 10 minutes)
* 2014-2015: Initial version
* Started at Linaro
* Dedicated to building upstream kernels for ARM
* 2016-2018: Emergence
* Boot testing in LAVA labs
* More build capacity with VMs, more labs
* Automated bisections
* 2019: Linux Foundation
* Launched with founding members
* Still more-or-less the same member companies today
* Drastic change of scope for the project, whole upstream kernel
* 2020-2021: Ramping up
* Kubernetes clusters for builds
* Functional testing
* ChromeOS
* KCIDB
* Community survey and new design PoC as a result
* 2022-2023: New API
* Updating the overall design to better serve the community
* Modular API PoC
* Preparation for new web dashboard
* Unifying use-cases with a single KernelCI tool set
* Part 2: Guided Tour
(main part)
* Current build capacity
* Current functional testing capacity
* KCIDB stats
* New API roadmap and current status
* New web dashboard efforts
* Overall impact
* Cherry-picked stories about bugs reported and fixed
* Growing community
* Pre-merge testing with BPF CI (Meta)
* Collaborations with Pengutronix, TI, ARM
* Rust support
* Side topics
* regzbot
* GitLab CI
* Manual kernel bug reports
* End users
* How to engage with KernelCI
* kci command line tool
* Web dashboard requirements and user stories
* Empowering users: from manual custom tests to full automation
* Part 3: Horizon for 2024
(discussion)
* Challenges
* New API roadmap delayed
* New web dashboard progress gated by new API
* Transition period with new team members (TSC, board)
* Advanced features to be unlocked
* Performance testing (measurements, stats)
* Advanced bisection based on stats (Scalpel PoC)
* Dynamic scheduling to run jobs based on results and available hw
* Post-regression checks beyond bisections
reply other threads:[~2024-03-03 22:35 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=71f59a56-aef3-4bae-867b-769a0cdd1c1b@gtucker.io \
--to=gtucker@gtucker.io \
--cc=automated-testing@lists.yoctoproject.org \
--cc=kernelci-members@groups.io \
--cc=kernelci-tsc@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
/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).