From: Vignesh Raman <vignesh.raman@collabora.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: dri-devel@lists.freedesktop.org, daniels@collabora.com,
helen.fornazier@gmail.com, airlied@gmail.com,
simona.vetter@ffwll.ch, robdclark@gmail.com,
dmitry.baryshkov@linaro.org, guilherme.gallo@collabora.com,
sergi.blanch.torne@collabora.com, valentine.burley@collabora.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] drm/ci: fix merge request rules
Date: Wed, 26 Feb 2025 20:08:45 +0530 [thread overview]
Message-ID: <84bd530c-4fb9-4913-8ee1-78a6a4f46625@collabora.com> (raw)
In-Reply-To: <CAPj87rNAaPUEmk1edcuHX1+bMWysF=aOMceUsCxnk2SMJUjqKg@mail.gmail.com>
Hi Daniel,
On 26/02/25 19:29, Daniel Stone wrote:
> Hi Vignesh,
>
> On Wed, 26 Feb 2025 at 13:55, Vignesh Raman <vignesh.raman@collabora.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.
mesa has on_success for is-direct-push. Should we change it to manual
here and update the same in mesa ?
If a user creates a MR, should the jobs run automatically, since we do
not use marge-bot to merge MRs in drm?
I also noticed we need to remove reference to mesa
(CI_PROJECT_NAMESPACE). I will send v2 with this change.
Regards,
Vignesh
>
> Cheers,
> Daniel
prev parent reply other threads:[~2025-02-26 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 13:53 Vignesh Raman
2025-02-26 13:59 ` Daniel Stone
2025-02-26 14:38 ` Vignesh Raman [this message]
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=84bd530c-4fb9-4913-8ee1-78a6a4f46625@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=daniel@fooishbar.org \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.fornazier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=simona.vetter@ffwll.ch \
--cc=valentine.burley@collabora.com \
/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
all inboxes | Powered by JetHome®