From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6 2/4] ci: add patchwork communication script
Date: Tue, 15 Apr 2025 17:36:25 +0200 [thread overview]
Message-ID: <Z_58-c488Qb3dkYn@yuki.lan> (raw)
In-Reply-To: <20250415-patchwork_ci-v6-2-81e6d4184af5@suse.com>
Hi!
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> ci/tools/patchwork.sh | 169 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 169 insertions(+)
>
> diff --git a/ci/tools/patchwork.sh b/ci/tools/patchwork.sh
> new file mode 100755
> index 0000000000000000000000000000000000000000..bef6998b6168714e0cfaef443a4573017440bb2d
> --- /dev/null
> +++ b/ci/tools/patchwork.sh
> @@ -0,0 +1,169 @@
> +#!/bin/sh -x
> +# SPDX-License-Identifier: GPL-2.0-or-later
> +#
> +# Shell script to communicate with Patchwork via REST API.
> +# It has been mainly created for CI purposes, but it can be used in the shell
> +# by satisfying minimum requirements.
> +#
> +# Copyright (c) 2025 Andrea Cervesato <andrea.cervesato@suse.com>
> +
> +PATCHWORK_URL="${PATCHWORK_URL:-https://patchwork.ozlabs.org}"
> +PATCHWORK_SINCE="${PATCHWORK_SINCE:-3600}"
> +
> +command_exists() {
> + for cmd in "$@"; do
> + if ! command -v "$cmd" >/dev/null 2>&1; then
> + echo "'$1' must be present in the system" >&2
> + exit 1
> + fi
> + done
> +}
> +
> +command_exists "curl" "jq"
> +
> +fetch_series() {
> + local current_time=$(date +%s)
> + local since_time=$(expr $current_time - $PATCHWORK_SINCE)
> + local date=$(date -u -d @$since_time +"%Y-%m-%dT%H:%M:%SZ")
> +
> + curl -k -G "$PATCHWORK_URL/api/events/" \
> + --data "category=series-completed" \
> + --data "project=ltp" \
> + --data "state=new" \
> + --data "since=$date" \
> + --data "archive=no" |
> + jq -r '.[] | "\(.payload.series.id):\(.payload.series.mbox)"'
^
We add ':' here and then we have to use IFS=':' to parse these values.
Wouldn't this work without the need to fiddle with IFS if we just added
space here instead?
If that worked we could get rid of all the IFS= assigments in the
script.
> + [ $? -eq 0 ] || exit 1
> +}
> +
> +get_patches() {
> + local series_id="$1"
> +
> + curl -k -G "$PATCHWORK_URL/api/patches/" \
> + --data "project=ltp" \
> + --data "series=$series_id" |
> + jq -r '.[] | "\(.id)"'
> +
> + [ $? -eq 0 ] || exit 1
> +}
> +
> +verify_token_exists() {
> + if [ -z "$PATCHWORK_TOKEN" ]; then
> + echo "For this feature you need \$PATCHWORK_TOKEN"
> + exit 1
> + fi
> +}
> +
> +set_patch_state() {
> + local patch_id="$1"
> + local state="$2"
> +
> + verify_token_exists
> +
> + curl -k -X PATCH \
> + -H "Authorization: Token $PATCHWORK_TOKEN" \
> + -F "state=$state" \
> + "$PATCHWORK_URL/api/patches/$patch_id/"
> +
> + [ $? -eq 0 ] || exit 1
> +}
> +
> +set_series_state() {
> + local series_id="$1"
> + local state="$2"
> +
> + get_patches "$series_id" | while IFS= read -r patch_id; do
> + [ "$patch_id" ] && set_patch_state "$patch_id" "$state"
> + done
> +}
> +
> +get_checks() {
> + local patch_id="$1"
> +
> + curl -k -G "$PATCHWORK_URL/api/patches/$patch_id/checks/" |
> + jq -r '.[] | "\(.id)"'
> +
> + [ $? -eq 0 ] || exit 1
> +}
> +
> +already_tested() {
> + local series_id="$1"
> +
> + get_patches "$series_id" | while IFS= read -r patch_id; do
> + [ "$patch_id" ] || continue
> +
> + get_checks "$patch_id" | while IFS= read -r check_id; do
> + if [ -n "$check_id" ]; then
> + echo "$check_id"
> + return
> + fi
> + done
> + done
> +}
> +
> +verify_new_patches() {
> + local tmp=$(mktemp -d)
> + local output="$tmp/series_ids.txt"
> +
> + echo -n '' >"$output"
> +
> + fetch_series | while IFS=: read -r series_id series_mbox; do
> + [ "$series_id" ] || continue
> +
> + tested=$(already_tested "$series_id")
> + [ "$tested" ] && continue
> +
> + echo "$series_id|$series_mbox" >>"$output"
> + done
> +
> + cat "$output"
> +}
> +
> +send_results() {
> + local series_id="$1"
> + local target_url="$2"
> +
> + verify_token_exists
> +
> + local context=$(echo "$3" | sed 's/:/_/g; s/\//-/g; s/\./-/g')
> +
> + [ "$CC" ] && context="${context}_${CC}"
> + [ "$ARCH" ] && context="${context}_${ARCH}"
> +
> + local result="$4"
> + [ "$result" == "cancelled" ] && return
> +
> + local state="fail"
> + [ "$result" == "success" ] && state="success"
> +
> + get_patches "$series_id" | while IFS= read -r patch_id; do
> + [ "$patch_id" ] || continue
> +
> + curl -k -X POST \
> + -H "Authorization: Token $PATCHWORK_TOKEN" \
> + -F "state=$state" \
> + -F "context=$context" \
> + -F "target_url=$target_url" \
> + -F "description=$result" \
> + "$PATCHWORK_URL/api/patches/$patch_id/checks/"
> +
> + [ $? -eq 0 ] && exit 1
> + done
> +}
> +
> +case "$1" in
> +state)
> + set_series_state "$2" "$3"
> + ;;
> +check)
> + send_results "$2" "$3" "$4" "$5"
> + ;;
> +verify)
> + verify_new_patches
> + ;;
> +*)
> + echo "Available commands: state, check, verify"
Possibly write this to stderr (&>2)?
> + exit 1
> + ;;
> +esac
Other than these:
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-04-15 15:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 10:00 [LTP] [PATCH v6 0/4] Support for Patchwork CI Andrea Cervesato
2025-04-15 10:00 ` [LTP] [PATCH v6 1/4] ci: install dependences for patchwork-ci script Andrea Cervesato
2025-04-15 14:45 ` Cyril Hrubis
2025-04-15 10:00 ` [LTP] [PATCH v6 2/4] ci: add patchwork communication script Andrea Cervesato
2025-04-15 13:48 ` pvorel
2025-04-15 15:36 ` Cyril Hrubis [this message]
2025-04-15 10:00 ` [LTP] [PATCH v6 3/4] ci: add ci-patchwork-trigger workflow Andrea Cervesato
2025-04-15 13:53 ` pvorel
2025-04-15 15:12 ` Cyril Hrubis
2025-04-15 16:10 ` Andrea Cervesato via ltp
2025-04-15 10:00 ` [LTP] [PATCH v6 4/4] ci: apply patchwork series in ci-docker-build workflow Andrea Cervesato
2025-04-15 13:55 ` pvorel
2025-04-15 16:34 ` Cyril Hrubis
2025-04-15 16:37 ` 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=Z_58-c488Qb3dkYn@yuki.lan \
--to=chrubis@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.