From: Vignesh Raman <vignesh.raman@collabora.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: dri-devel@lists.freedesktop.org, daniels@collabora.com,
helen.fornazier@gmail.com, airlied@gmail.com,
simona.vetter@ffwll.ch, robdclark@gmail.com,
guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
valentine.burley@collabora.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/ci: fix merge request rules
Date: Fri, 28 Feb 2025 18:08:04 +0530 [thread overview]
Message-ID: <e8e7de99-ade8-48ca-804c-58ce3fedad4b@collabora.com> (raw)
In-Reply-To: <ondpwjsgujhk7wo3gaajoeamcf4gkp424cxmyslwsybrlkzo5f@xh3yx2r2mp6k>
Hi Dmitry,
On 28/02/25 12:28, Dmitry Baryshkov wrote:
> On Thu, Feb 27, 2025 at 09:50:50AM +0530, Vignesh Raman 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.
>>
>> Run jobs automatically for marge-bot and scheduled
>> pipelines, but in all other cases run manually. Also
>> remove CI_PROJECT_NAMESPACE checks specific to mesa.
>>
>> Fixes: df54f04f2020 ("drm/ci: update gitlab rules")
>> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
>> ---
>>
>> v2:
>> - Run jobs automatically for marge-bot and scheduled
>> pipelines, but in all other cases run manually. Also
>> remove CI_PROJECT_NAMESPACE checks specific to mesa.
>>
>> ---
>> drivers/gpu/drm/ci/gitlab-ci.yml | 21 +++++----------------
>> 1 file changed, 5 insertions(+), 16 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/ci/gitlab-ci.yml b/drivers/gpu/drm/ci/gitlab-ci.yml
>> index f04aabe8327c..f4e324e156db 100644
>> --- a/drivers/gpu/drm/ci/gitlab-ci.yml
>> +++ b/drivers/gpu/drm/ci/gitlab-ci.yml
>> @@ -143,11 +143,11 @@ stages:
>> # Pre-merge pipeline
>> - if: &is-pre-merge $CI_PIPELINE_SOURCE == "merge_request_event"
>> # Push to a branch on a fork
>> - - if: &is-fork-push $CI_PROJECT_NAMESPACE != "mesa" && $CI_PIPELINE_SOURCE == "push"
>> + - if: &is-fork-push $CI_PIPELINE_SOURCE == "push"
>> # nightly pipeline
>> - if: &is-scheduled-pipeline $CI_PIPELINE_SOURCE == "schedule"
>> # pipeline for direct pushes that bypassed the CI
>> - - if: &is-direct-push $CI_PROJECT_NAMESPACE == "mesa" && $CI_PIPELINE_SOURCE == "push" && $GITLAB_USER_LOGIN != "marge-bot"
>> + - if: &is-direct-push $CI_PIPELINE_SOURCE == "push" && $GITLAB_USER_LOGIN != "marge-bot"
>>
>>
>> # Rules applied to every job in the pipeline
>> @@ -170,26 +170,15 @@ stages:
>> - !reference [.disable-farm-mr-rules, rules]
>> # Never run immediately after merging, as we just ran everything
>> - !reference [.never-post-merge-rules, rules]
>> - # Build everything in merge pipelines, if any files affecting the pipeline
>> - # were changed
>> + # Build everything in merge pipelines
>> - if: *is-merge-attempt
>> - changes: &all_paths
>> - - drivers/gpu/drm/ci/**/*
>> when: on_success
>> # Same as above, but for pre-merge pipelines
>> - if: *is-pre-merge
>> - changes:
>> - *all_paths
>> - when: manual
>> - # Skip everything for pre-merge and merge pipelines which don't change
>> - # anything in the build
>> - - if: *is-merge-attempt
>> - when: never
>> - - if: *is-pre-merge
>> - when: never
>> + - when: manual
>
> I believe there should be no dash on this line
>
>> # Build everything after someone bypassed the CI
>> - if: *is-direct-push
>> - when: on_success
>> + - when: manual
>
> And on this line too.
Thanks for spotting this. Will fix and send v3.
Regards,
Vignesh
>
>> # Build everything in scheduled pipelines
>> - if: *is-scheduled-pipeline
>> when: on_success
>> --
>> 2.47.2
>>
>
prev parent reply other threads:[~2025-02-28 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 4:20 Vignesh Raman
2025-02-27 12:46 ` Helen Mae Koike Fornazier
2025-02-28 6:58 ` Dmitry Baryshkov
2025-02-28 12: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=e8e7de99-ade8-48ca-804c-58ce3fedad4b@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--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®