RE: Community CI Meeting Minutes November 18, 2021

[Ali Alnubani <alialnu@nvidia.com>]

Hello,
Sorry for the delayed update,

> -----Original Message-----
> From: Lincoln Lavoie <lylavoie@iol.unh.edu>
> Sent: Thursday, November 18, 2021 5:25 PM
> To: ci@dpdk.org
> Subject: Community CI Meeting Minutes November 18, 2021
> 
> DPDK Community CI Meeting Minutes
> 
> Nov 18, 2021
> 
[..]
> ---------------------------------------------------------------------
> Intel Lab
> 
> * Planning downtime for after 21.11 release for lab migration.
> * Rerun requests: What is the maximum query rate allowed by patchwork?
> The
> overall issue is supporting a common mechanism across the different test
> infrastructures.  Ali will double check if events could be possible in
> patchworks.  Otherwise, we could create a micro-service to do the polling
> solution, and that service generates the events.  Could also put a "script
> / bot" between the mailman and patchworks.

I still believe that modifying Patchwork's events API will require changing Patchwork's Django models, which is going to break future Patchwork upgrades if these changes aren't in upstream first.
Implementing a microservice with HTTP push API (webhook) to callback publicly accessible URLs in the labs might be the best solution and won't have to live in the Patchwork server, it could be in any other lab.
It could callback existing apps/services in the different labs that currently monitor patch state changes using events polling. It can also parse mailing list posts to look for comments that trigger retesting. For the second part, if you don't want to crawl the mailing list archives, a receiving postfix mail server can be configured to deliver mailing list posts to an external command using a pipe postfix service. The external command in this case would be a script that parses the incoming emails.

Please reach out if there is anything I can help with.

Thanks,
Ali