DPDK CI discussions
 help / color / Atom feed
* [dpdk-ci] Patchwork setup
@ 2019-11-01  9:08 Petr Vorel
  2019-11-01  9:39 ` Thomas Monjalon
  0 siblings, 1 reply; 5+ messages in thread
From: Petr Vorel @ 2019-11-01  9:08 UTC (permalink / raw)
  To: ci; +Cc: Thomas Monjalon, Ferruh Yigit

Hi,

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?
Did you just manually added travis button to the django template (I guess there is no
UI setup for it)?
Did you implemented posts to S/W/F via REST API [1]?

Thanks,
Petr

[1] https://patchwork.readthedocs.io/en/latest/api/rest/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [dpdk-ci] Patchwork setup
  2019-11-01  9:08 [dpdk-ci] Patchwork setup Petr Vorel
@ 2019-11-01  9:39 ` Thomas Monjalon
  2019-11-01 10:32   ` Petr Vorel
  0 siblings, 1 reply; 5+ messages in thread
From: Thomas Monjalon @ 2019-11-01  9:39 UTC (permalink / raw)
  To: Petr Vorel; +Cc: ci, Ferruh Yigit, alialnu

01/11/2019 10:08, Petr Vorel:
> Hi,
> 
> 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?


> 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



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [dpdk-ci] Patchwork setup
  2019-11-01  9:39 ` Thomas Monjalon
@ 2019-11-01 10:32   ` Petr Vorel
  2019-11-01 14:50     ` Thomas Monjalon
  0 siblings, 1 reply; 5+ messages in thread
From: Petr Vorel @ 2019-11-01 10:32 UTC (permalink / raw)
  To: Thomas Monjalon; +Cc: ci, Ferruh Yigit, alialnu

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [dpdk-ci] Patchwork setup
  2019-11-01 10:32   ` Petr Vorel
@ 2019-11-01 14:50     ` Thomas Monjalon
  2019-11-01 15:19       ` Petr Vorel
  0 siblings, 1 reply; 5+ messages in thread
From: Thomas Monjalon @ 2019-11-01 14:50 UTC (permalink / raw)
  To: Petr Vorel; +Cc: ci, Ferruh Yigit, alialnu

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.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [dpdk-ci] Patchwork setup
  2019-11-01 14:50     ` Thomas Monjalon
@ 2019-11-01 15:19       ` Petr Vorel
  0 siblings, 0 replies; 5+ messages in thread
From: Petr Vorel @ 2019-11-01 15:19 UTC (permalink / raw)
  To: Thomas Monjalon; +Cc: ci, Ferruh Yigit, alialnu

Hi Thomas,

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

Good, that makes things much easier.

Thanks for all info.

Kind regards,
Petr

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, back to index

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-01  9:08 [dpdk-ci] Patchwork setup Petr Vorel
2019-11-01  9:39 ` Thomas Monjalon
2019-11-01 10:32   ` Petr Vorel
2019-11-01 14:50     ` Thomas Monjalon
2019-11-01 15:19       ` Petr Vorel

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox