DPDK CI discussions
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>, alialnu@mellanox.com
Subject: Re: [dpdk-ci] Patchwork setup
Date: Fri, 1 Nov 2019 11:32:18 +0100	[thread overview]
Message-ID: <20191101103217.GA25242@dell5510> (raw)
In-Reply-To: <2279949.o5Xao51OsT@xps>

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).


> > 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.

Kind regards,
Petr

  reply	other threads:[~2019-11-01 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01  9:08 Petr Vorel
2019-11-01  9:39 ` Thomas Monjalon
2019-11-01 10:32   ` Petr Vorel [this message]
2019-11-01 14:50     ` Thomas Monjalon
2019-11-01 15:19       ` Petr Vorel

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=20191101103217.GA25242@dell5510 \
    --to=pvorel@suse.cz \
    --cc=alialnu@mellanox.com \
    --cc=ci@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).