linux-kernel - Re: [PATCH v1] drm/ci: fix merge request rules

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: <CAPj87rNAaPUEmk1edcuHX1+bMWysF=aOMceUsCxnk2SMJUjqKg@mail.gmail.com>
Date: Wed, 26 Feb 2025 13:59:15 +0000
From: Daniel Stone <daniel@...ishbar.org>
To: Vignesh Raman <vignesh.raman@...labora.com>
Cc: dri-devel@...ts.freedesktop.org, daniels@...labora.com, 
	helen.fornazier@...il.com, airlied@...il.com, simona.vetter@...ll.ch, 
	robdclark@...il.com, dmitry.baryshkov@...aro.org, 
	guilherme.gallo@...labora.com, sergi.blanch.torne@...labora.com, 
	valentine.burley@...labora.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] drm/ci: fix merge request rules

Hi Vignesh,

On Wed, 26 Feb 2025 at 13:55, Vignesh Raman <vignesh.raman@...labora.com> wrote:
> Merge request pipelines were only created when changes
> were made to drivers/gpu/drm/ci/, causing MRs that didn't
> touch this path to break. Fix MR pipeline rules to trigger
> jobs for all changes.

Thanks a lot for fixing this up!

>      # Build everything after someone bypassed the CI
>      - if: *is-direct-push
>        when: on_success

Should these be when: manual? I think it would be good to align with
the rules we have for Mesa: run automatically for marge-bot and also
for scheduled pipelines, but in all other cases (MR context but not
scheduled for merge, direct push to ref, etc) be manual, so we don't
overwhelm the CI by testing everything everyone pushed.

Cheers,
Daniel