All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 0/4] Support for Patchwork CI
Date: Fri, 11 Apr 2025 14:07:14 +0200	[thread overview]
Message-ID: <20250411120714.GA319294@pevik> (raw)
In-Reply-To: <20250411114326.526-1-andrea.cervesato@suse.de>

Hi all,

> Add support for patch-series validation in the patchwork ML.
> We use Github to schedule a trigger every 30 minutes, checking for new
> patche-series in parchwork which has not been tested yet.

> The way we decide if a patch-series has been tested in patchwork, is
> by looking at its status (in particular, if it's "Needs Review / ACK"),
> as well as checking if test report has been uploaded to any of the
> series patches.

> All communication to Patchwrok is done via REST API, using curl and js
> tools.

> First, we create a script called patchwork-ci.sh that provides all the
> commands to read new untested patch-series, set their status and testing
> report. Then, we create a scheduled workflow in Gitlab, checking every
> 30 minutes if there are new untested patch-series. At the end, we
> trigger the main build workflow, used to validate LTP commits in our
> Github mainline. All the times we trigger the build workflow, we also
> provide the patch-series ID, that will be fetched and applied on the
> current branch before running the tests.

> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> Changes in v4:
> - patchwork script is now a tool that can be used independently to ci

> Andrea Cervesato (4):
>   ci: install dependences for patchwork-ci script
>   ci: add patchwork communication script
>   ci: add ci-patchwork-trigger workflow

Andrea did a great effort. Unfortunately we deal with problem probably caused by
our mailing list because 3rd commit "ci: add ci-patchwork-trigger workflow" did
not arrive to mailing list.

I suppose the branch is visible on Andrea's fork:

https://github.com/acerv/ltp/tree/refs/heads/b4/patchwork_ci

Mail is not in "ending moderator requests" on https://lists.linux.it/,
I guess we need to contact ML administrators, I'll do it and Cc you.

Kind regards,
Petr

>   ci: apply patchwork series in ci-docker-build workflow

>  .github/workflows/ci-docker-build.yml      |  39 +++-
>  .github/workflows/ci-patchwork-trigger.yml |  63 +++++++
>  ci/alpine-runtime.sh                       |   2 +
>  ci/alpine.sh                               |   2 +
>  ci/debian.i386.sh                          |   2 +
>  ci/debian.sh                               |  28 +--
>  ci/fedora.sh                               |   2 +
>  ci/tools/patchwork.sh                      | 197 +++++++++++++++++++++
>  ci/tumbleweed.sh                           |   2 +
>  9 files changed, 323 insertions(+), 14 deletions(-)
>  create mode 100644 .github/workflows/ci-patchwork-trigger.yml
>  create mode 100755 ci/tools/patchwork.sh

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2025-04-11 12:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 11:43 [LTP] [PATCH v5 0/4] Support for Patchwork CI Andrea Cervesato
2025-04-11 11:43 ` [LTP] [PATCH v5 1/4] ci: install dependences for patchwork-ci script Andrea Cervesato
2025-04-14 12:51   ` Petr Vorel
2025-04-14 13:00     ` Andrea Cervesato via ltp
2025-04-11 11:43 ` [LTP] [PATCH v5 2/4] ci: add patchwork communication script Andrea Cervesato
2025-04-14 14:02   ` Petr Vorel
2025-04-15  8:50     ` Andrea Cervesato via ltp
2025-04-15  9:04       ` Petr Vorel
2025-04-11 11:43 ` [LTP] [PATCH v5 4/4] ci: apply patchwork series in ci-docker-build workflow Andrea Cervesato
2025-04-11 12:07 ` Petr Vorel [this message]
2025-04-11 12:10   ` [LTP] [PATCH v5 0/4] Support for Patchwork CI Cyril Hrubis
2025-04-11 12:59     ` Petr Vorel
2025-04-11 13:06       ` Andrea Cervesato via ltp
2025-04-14 15:41 ` Petr Vorel
2025-04-15  7:53   ` Andrea Cervesato via ltp
2025-04-15  9:49     ` Petr Vorel
2025-04-15  9:54       ` Andrea Cervesato via ltp

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=20250411120714.GA319294@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.