[dpdk-ci] Patchwork setup

[Thomas Monjalon]

01/11/2019 11:32, Petr Vorel:
> Hi Thomas,
> 
> thanks for a quick info!
> 
> > > I really like your patchwork setup (travis CI button and posted CI build results
> > > to S/W/F column).
> > > Would you mind sharing your setup?
> 
> > These are just simple local patches to customize the UI.
> > Feel free to contact directly Ali and me for more details.
> 
> > Which patchwork instance are you interested in?
> I'm interested to improve our LTP patchwork instance on ozlabs
> https://patchwork.ozlabs.org/project/ltp/list/
> There are many project hosted, so direct modification isn't possible.
> The easiest way would be to host our own instance ourselves, but we don't want.
> I might extend patchwork DB schema to allow setup custom HTML snippet for
> particular instance (long term solution and button is less important than S/W/F).

Yes more configuration may be nice.

> > > Did you just manually added travis button to the django template (I guess there is no
> > > UI setup for it)?
> 
> > Yes, it is manually added.
> 
> 
> > > Did you implemented posts to S/W/F via REST API [1]?
> 
> > No, it was done with RPC (pwclient) when REST was not available.
> > The script is in this git:
> > 	http://git.dpdk.org/tools/dpdk-ci/tree/tools/update-pw.sh
> Thanks for pointing to this script. I suppose either your solution or REST API
> requires using cron, so this might force us to move from ozlabs to self hosting
> patchwork instance.

You can keep your ozlabs instance and run the script anywhere.
The only requirement is to wait for the test report to be received,
so you can send a public URL of the report to patchwork.