Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
"Jarkko Sakkinen" <[email protected]> Thu, 23 Jan 2025 23:30:40 +0200
| Newsgroups | dev.linux.lists.kernelci,fr.inria.cocci,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kernel.vger.workflows |
|---|---|
| Message-ID | <[email protected]> |
On Thu Jan 23, 2025 at 3:53 PM EET, Vignesh Raman wrote: > We are working towards creating a generic, upstream GitLab-CI pipeline > (kci-gitlab) that will replace DRM-CI [1]. The proposed GitLab-CI pipeline > is designed with a distributed infrastructure model, making it possible > to run on any gitLab instance. We plan to leverage KernelCI [2] as the > backend, utilizing its hardware, rootfs, test plans, and KCIDB [3] > integration. Why can't you keep the next version of your great pipeline outside the kernel tree? If there is a legit motivation for doing that, why it needs to be bound to Gitlab? Why can't you make script callable from any CI? BR, Jarkko