From: "Krzysztof Wilczyński" <krzysztof.wilczynski@collabora.com>
To: Gustavo Padovan <gustavo.padovan@collabora.com>
Cc: "Dan Williams" <dan.j.williams@intel.com>,
"Daniel Stone" <daniel.stone@collabora.com>,
"Denys Fedoryshchenko" <denys.f@collabora.com>,
"Mark Brown" <broonie@kernel.org>,
"Paweł Wieczorek" <pawel.wieczorek@collabora.com>,
"Linux Kernel Selftests" <linux-kselftest@vger.kernel.org>,
"Automated Testing" <automated-testing@lists.yoctoproject.org>,
"KernelCI Hardware Vendors" <kernelci-hw-vendors@groups.io>,
KernelCI <kernelci@lists.linux.dev>
Subject: Support for .kernelci.yaml file for in-tree configuration
Date: Mon, 28 Apr 2025 17:37:06 +0900 [thread overview]
Message-ID: <20250428083706.GA691378@rocinante> (raw)
Hello everyone,
A heads up!
Work on moving some aspects of the KernelCI configuration into an in-tree
(or per-project, if you wish) file called ".kernelci.yaml" has started and
is currently in the early design and implementation stage.
This is why we need your feedback to ensure that the feature implementation
moves in the right direction and will meet the user's needs.
Please have a look at the following GitHub issue:
https://github.com/kernelci/kernelci-pipeline/issues/1126
The linked issue is where anyone interested in this feature can get
involved to discuss implementation details, ask questions, etc. You can,
of course, ask questions here, too.
This new feature will eventually pave the way for the introduction of
a push model to KernelCI, along with the pull model we currently have,
allowing for the integration of different Git hosting platforms, such as
GitHub, GitLab, etc., where events sent to us from these platforms will
trigger an appropriate behaviour on the KernelCI's side.
However, this new functionality will be added as a mid-term deliverable,
where the ability to configure KernelCI via the ".kernelci.yaml" file is
one of the crucial dependencies.
Please don't hesitate to get involved and provide feedback.
Thank you!
On behalf of the KernelCI maintainers,
Krzysztof
reply other threads:[~2025-04-28 8:37 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=20250428083706.GA691378@rocinante \
--to=krzysztof.wilczynski@collabora.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=daniel.stone@collabora.com \
--cc=denys.f@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=kernelci-hw-vendors@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-kselftest@vger.kernel.org \
--cc=pawel.wieczorek@collabora.com \
/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).