From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 07E6316EC19; Thu, 23 Jan 2025 21:30:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737667847; cv=none; b=ZnX9GkpbjeUSrEKVabfrpIcbqMe+6S5Xii9Hf8/V5Uq4Msv7VnHW0NDp7lTOs+0nYCZRhsMZ/PP1TpVUWBxdg0Hn9zIGcONFi1k1SvKAq4xCLVVMAtEiIesBOLkl66RTiuuq5F3492VmPywGqc/wXF25SIKuVBHt4YLzZRFYKRw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737667847; c=relaxed/simple; bh=929SbkPZ1rHZGzLzkzfyL8bQgeP/Kh91Wpz1dFourKM=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:Subject:From:To: References:In-Reply-To; b=oqAR+PCfHk4zc2e7BOX1aanWJpl2VV9zpLcPNG4/snA2RdK1Lg3CSqCNJEMNEN4zbF7Er+kq5oZ03vDpvswq/86T6f+kDc5t4PHKdBxRgOE+QUUwyYJy1oGzvf+xuxraUqZUXRzvpY65yUaKMRslTDSG7quIoDR83HJIQwcvBEg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ma4Qyk7m; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ma4Qyk7m" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B2D00C4CED3; Thu, 23 Jan 2025 21:30:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1737667846; bh=929SbkPZ1rHZGzLzkzfyL8bQgeP/Kh91Wpz1dFourKM=; h=Date:Cc:Subject:From:To:References:In-Reply-To:From; b=ma4Qyk7mEhcwihmS3b+DFhOCXJEno6SD0X4g8jNX14SQHHum/jftVXnUCHAxXyJtj 9SCAboLAP8ky3xalfX1MbyKuArL+iM3esKuGwRSrPAj1qCmgkCadWn5cTMndCiG/N1 RomQpgO5gpQOVLLUNtM5AIFSKhHWhrOUwVYrG4aVlhwu4lRAOVQDuNhTw84HqZTrQS s68Ut3F0dPYC5upgmdHekKp+ta38/e+bzO7J+CV3WCyD1RlM1k21fS5czBOV6e3IEu UdqLHrUXpiwCWTFe33OduOL4KpBZ9aBUrqPmvzthFGqUnxzooQoE8UIgTWiFdIHwf0 lRL//4PJcktsA== Precedence: bulk X-Mailing-List: workflows@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 23 Jan 2025 23:30:40 +0200 Message-Id: Cc: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing From: "Jarkko Sakkinen" To: "Vignesh Raman" , X-Mailer: aerc 0.18.2 References: <20250123135342.1468787-1-vignesh.raman@collabora.com> 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 pipelin= e > 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