[LTP] [PATCH v5 0/4] Support for Patchwork CI
Andrea Cervesato
andrea.cervesato@suse.de
Fri Apr 11 13:43:20 CEST 2025
From: Andrea Cervesato <andrea.cervesato@suse.com>
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
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
--
2.43.0
More information about the ltp
mailing list