From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Vignesh Raman" <vignesh.raman@collabora.com>,
<kernelci@lists.linux.dev>
Cc: <linuxtv-ci@linuxtv.org>, <dave.pigott@collabora.com>,
<mripard@kernel.org>, <linux-kernel@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<linux-kselftest@vger.kernel.org>,
<gustavo.padovan@collabora.com>, <pawiecz@collabora.com>,
<spbnick@gmail.com>, <tales.aparecida@gmail.com>,
<workflows@vger.kernel.org>, <skhan@linuxfoundation.org>,
<kunit-dev@googlegroups.com>, <nfraprado@collabora.com>,
<davidgow@google.com>, <cocci@inria.fr>, <Julia.Lawall@inria.fr>,
<laura.nao@collabora.com>, <kernel@collabora.com>,
<torvalds@linuxfoundation.org>, <gregkh@linuxfoundation.org>,
<daniels@collabora.com>, <helen.koike@collabora.com>,
<shreeya.patel@collabora.com>, <denys.f@collabora.com>,
<nicolas.dufresne@collabora.com>, <louis.chauvet@bootlin.com>,
<hamohammed.sa@gmail.com>, <melissa.srw@gmail.com>,
<simona@ffwll.ch>, <airlied@gmail.com>, <Tim.Bird@sony.com>,
<laurent.pinchart@ideasonboard.com>, <broonie@kernel.org>,
<leobras.c@gmail.com>, <groeck@google.com>,
<rdunlap@infradead.org>, <geert@linux-m68k.org>,
<michel.daenzer@mailbox.org>, <sakari.ailus@iki.fi>
Subject: Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
Date: Thu, 23 Jan 2025 23:30:40 +0200 [thread overview]
Message-ID: <D79RU9MHGKJ8.1HG89ZJS4Q5FC@kernel.org> (raw)
In-Reply-To: <20250123135342.1468787-1-vignesh.raman@collabora.com>
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
next prev parent reply other threads:[~2025-01-23 21:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 13:53 Vignesh Raman
2025-01-23 13:53 ` [PATCH v2 1/5] " Vignesh Raman
2025-01-23 13:53 ` [PATCH v2 2/5] MAINTAINERS: Add an entry for ci automated testing Vignesh Raman
2025-01-23 13:53 ` [PATCH v2 3/5] kci-gitlab: Add drm scenario Vignesh Raman
2025-01-23 20:06 ` Simona Vetter
2025-01-24 12:37 ` Helen Mae Koike Fornazier
2025-01-24 15:31 ` Simona Vetter
2025-01-27 4:07 ` Vignesh Raman
2025-01-23 13:53 ` [PATCH v2 4/5] kci-gitlab: Add documentation Vignesh Raman
2025-01-23 13:53 ` [PATCH v2 5/5] kci-gitlab: docs: Add images Vignesh Raman
2025-01-23 15:46 ` Linus Torvalds
2025-01-23 18:04 ` Nicolas Dufresne
2025-01-27 3:56 ` Vignesh Raman
2025-01-23 21:30 ` Jarkko Sakkinen [this message]
2025-01-23 21:31 ` [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing Jarkko Sakkinen
2025-01-24 12:58 ` Nikolai Kondrashov
2025-01-24 16:32 ` Jarkko Sakkinen
2025-01-24 17:04 ` Nikolai Kondrashov
2025-01-24 17:15 ` Mark Brown
2025-01-24 17:34 ` Laurent Pinchart
2025-01-24 5:11 ` Leonardo Brás
2025-01-24 8:12 ` Laurent Pinchart
2025-01-24 12:16 ` Jarkko Sakkinen
2025-01-24 13:00 ` Nikolai Kondrashov
2025-01-24 14:26 ` Nicolas Dufresne
2025-01-24 15:29 ` Mauro Carvalho Chehab
2025-01-24 19:49 ` Helen Mae Koike Fornazier
2025-01-24 19:59 ` Bird, Tim
2025-01-27 6:39 ` Mauro Carvalho Chehab
2025-01-24 16:36 ` Jarkko Sakkinen
2025-01-24 12:52 ` Mauro Carvalho Chehab
2025-01-24 13:00 ` Laurent Pinchart
2025-01-24 15:45 ` Nicolas Dufresne
2025-01-24 21:12 ` Leonardo Brás
2025-01-27 6:07 ` Laurent Pinchart
2025-01-27 7:07 ` Mauro Carvalho Chehab
2025-01-27 14:43 ` Nicolas Dufresne
2025-01-27 16:23 ` Laurent Pinchart
2025-01-24 20:50 ` Leonardo Brás
2025-01-27 7:32 ` Vignesh Raman
2025-01-27 19:05 ` Leonardo Brás
2025-01-29 9:32 ` Vignesh Raman
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=D79RU9MHGKJ8.1HG89ZJS4Q5FC@kernel.org \
--to=jarkko@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=Tim.Bird@sony.com \
--cc=airlied@gmail.com \
--cc=broonie@kernel.org \
--cc=cocci@inria.fr \
--cc=daniels@collabora.com \
--cc=dave.pigott@collabora.com \
--cc=davidgow@google.com \
--cc=denys.f@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@google.com \
--cc=gustavo.padovan@collabora.com \
--cc=hamohammed.sa@gmail.com \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=kunit-dev@googlegroups.com \
--cc=laura.nao@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxtv-ci@linuxtv.org \
--cc=louis.chauvet@bootlin.com \
--cc=melissa.srw@gmail.com \
--cc=michel.daenzer@mailbox.org \
--cc=mripard@kernel.org \
--cc=nfraprado@collabora.com \
--cc=nicolas.dufresne@collabora.com \
--cc=pawiecz@collabora.com \
--cc=rdunlap@infradead.org \
--cc=sakari.ailus@iki.fi \
--cc=shreeya.patel@collabora.com \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=spbnick@gmail.com \
--cc=tales.aparecida@gmail.com \
--cc=torvalds@linuxfoundation.org \
--cc=vignesh.raman@collabora.com \
--cc=workflows@vger.kernel.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