linux-kernel - Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f9a3d871-dd51-453b-b510-d076ecf0fabd@gmail.com>
Date: Thu, 29 Feb 2024 16:12:41 +0200
From: Nikolai Kondrashov <spbnick@...il.com>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
 Guillaume Tucker <gtucker@...cker.io>
Cc: Mark Brown <broonie@...nel.org>, Helen Koike <helen.koike@...labora.com>,
 linuxtv-ci@...uxtv.org, dave.pigott@...labora.com, mripard@...nel.org,
 linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
 linux-kselftest@...r.kernel.org, gustavo.padovan@...labora.com,
 pawiecz@...labora.com, tales.aparecida@...il.com, workflows@...r.kernel.org,
 kernelci@...ts.linux.dev, skhan@...uxfoundation.org,
 kunit-dev@...glegroups.com, nfraprado@...labora.com, davidgow@...gle.com,
 cocci@...ia.fr, Julia.Lawall@...ia.fr, laura.nao@...labora.com,
 ricardo.canuelo@...labora.com, kernel@...labora.com,
 torvalds@...uxfoundation.org, gregkh@...uxfoundation.org
Subject: Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel
 Testing

On 2/29/24 2:25 PM, Laurent Pinchart wrote:
> On Thu, Feb 29, 2024 at 02:20:41PM +0200, Laurent Pinchart wrote:
>> On Thu, Feb 29, 2024 at 12:53:38PM +0100, Guillaume Tucker wrote:
>>> On 29/02/2024 12:41, Mark Brown wrote:
>>>> On Thu, Feb 29, 2024 at 01:19:19PM +0200, Laurent Pinchart wrote:
>>>>> On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote:
>>>>
>>>>>> Of course. You're also welcome to join the #kernelci channel on libera.chat.
>>>>
>>>>> Isn't that a bit pointless if it's no the main IM channel ?
>>>>
>>>> It *was* the original channel and still gets some usage (mostly started
>>>> by me admittedly since I've never joined slack for a bunch of reasons
>>>> that make it hassle), IIRC the Slack was started because there were some
>>>> interns who had trouble figuring out IRC and intermittent connectivity
>>>> but people seem to have migrated.
>>>
>>> In fact it was initially created for the members of the Linux
>>> Foundation project only, which is why registration is moderated
>>> for emails that don't have a domain linked to a member (BTW not
>>> any Google account will just work e.g. @gmail.com is moderated,
>>> only @google.com for Google employees isn't).
>>>
>>> And yes IRC is the "least common denominator" chat platform.
>>> Maybe having a bridge between the main Slack channel and IRC
>>> would help.
>>
>> If the gitlab CI pipeline proposal wants to be considered for inclusion
>> in the kernel, I think it needs to switch to a free software solution
>> for its *main* communication channels.
> 
> And to clarify, I didn't meant the kernel CI project, but only the
> gitlab CI pipeline for the Linux kernel project. I don't know how
> tightly integrated the two projects are though.

They're not tightly integrated so far. However, we're exploring the idea of 
letting GitLab CI submit jobs to KernelCI and get results as a part of the 
pipeline.

Helen already joined the #kernelci channel, and we will maintain a presence 
there for the GitLab CI project.

Nick