Re: Discussion: Moving away from Patchwork for Intel i915/Xe CI

[Jani Nikula <jani.nikula@linux.intel.com>]

On Wed, 05 Mar 2025, "Knop, Ryszard" <ryszard.knop@intel.com> wrote:
> The workflow would look like this:
>
> - A drm-tip mirror would be set up on GitHub/fd.o GitLab, automatically
> pulling all changes from drm-tip upstream fd.o GitLab as a secondary
> source.
> - For each new series on lore.kernel.org a bridge would create a PR by
> taking the latest mirrored drm-tip source, then applying a new series
> with `b4 shazam`.
> - That PR would then go through the normal CI flow, with CI checks
> being reported on that PR, instead of sending all the reports to the
> mailing list.
> - On the mailing list, the bridge would send an ack that a series has
> been seen and where are its results. You would no longer receive
> multiple emails with KBs of logs in your email client, but everything
> would be available from PR checks (as status checks and links to full
> logs only, no trimming and "last 1000 lines only").
> - Mirrors, PRs and checks for public mailing lists would be public,
> much like on the current public Patchwork instance.
> - Logs behind links will be stored for a few months (3-6, depends on
> traffic and how the situation evolves). GitHub Checks themselves (check
> status, shortlogs and links) have a hard retention period of 400 days.
> - Not sure about PR retention: we need a mechanism to correctly
> identify merged series somehow, then to trim these from the list.
> Expected retention time?

There's one feature I like about FDO patchwork that I'd like to be able
to retain. You can find the patches and thus the test results via a
message-id like this:

https://patchwork.freedesktop.org/patch/msgid/<message-id>

I use that from my MUA 100x more often than the series URL sent by
patchwork:

https://patchwork.freedesktop.org/series/<id>/

So I'd like to have a way to get from the patch/cover-letter message-id
to the github/gitlab MR or where ever the resuls are.

We currently add Link: tags to commits pointing at patchwork. There's
already been requests to switch to use Lore links instead, and I think
we should probably do that.

Finally, on sunsetting patchwork, I think a redirector from:

https://patchwork.freedesktop.org/patch/msgid/<message-id>

to:

https://lore.kernel.org/r/<message-id>

would be a nice thing to do, considering how many patchwork links we
have in commit messages.


BR,
Jani.


-- 
Jani Nikula, Intel