From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 65BBEA00BE for ; Fri, 1 Nov 2019 11:32:22 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 30BCC1DFE9; Fri, 1 Nov 2019 11:32:22 +0100 (CET) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) by dpdk.org (Postfix) with ESMTP id 744F81DFE7 for ; Fri, 1 Nov 2019 11:32:20 +0100 (CET) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id F30F8B670; Fri, 1 Nov 2019 10:32:19 +0000 (UTC) Date: Fri, 1 Nov 2019 11:32:18 +0100 From: Petr Vorel To: Thomas Monjalon Cc: ci@dpdk.org, Ferruh Yigit , alialnu@mellanox.com Message-ID: <20191101103217.GA25242@dell5510> References: <20191101090829.GA17463@dell5510> <2279949.o5Xao51OsT@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2279949.o5Xao51OsT@xps> User-Agent: Mutt/1.11.3 (2019-02-01) Subject: Re: [dpdk-ci] Patchwork setup X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Petr Vorel List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" 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