[dpdk-ci] script to determine target repo (was DPDK Lab)

[Xu, Qian Q]

Sent to correct Thomas' mail:), Thomas, could you see below? Thx. 

> -----Original Message-----
> From: Xu, Qian Q
> Sent: Tuesday, April 25, 2017 2:24 PM
> To: Thomas Monjalon <thomas.monjalon at 6wind.com>
> Cc: ci at dpdk.org; Richardson, Bruce <bruce.richardson at intel.com>; Wei,
> FangfangX <fangfangx.wei at intel.com>; O'Driscoll, Tim
> <tim.odriscoll at intel.com>; Liu, Yuanhan <yuanhan.liu at intel.com>; Xu, Qian Q
> <qian.q.xu at intel.com>
> Subject: RE: script to determine target repo (was DPDK Lab)
> 
> Thanks Thomas and Bruce for your comments. Currently we are trying to start
> the per patch set performance test investigation and need to know the Target
> repo for each patch set.
> The goal is to get 100% correct repo to go for each patch set. It's important for
> the credit of the performance result.
> @Thomas, could you provide any script to support the auto-filter after the 17.05
> release? Currently, we don't have the ability to make it.
> 
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > Sent: Thursday, April 13, 2017 2:46 PM
> > To: Xu, Qian Q <qian.q.xu at intel.com>
> > Cc: ci at dpdk.org; Richardson, Bruce <bruce.richardson at intel.com>
> > Subject: Re: script to determine target repo (was DPDK Lab)
> >
> > 2017-04-13 05:25, Xu, Qian Q:
> > > To do the per patchset performance test, we need to know that the
> > > patchset's
> > target repo. Any thoughts here?
> >
> > The first task is to extract modified files from lines starting with +++.
> > Then we must apply some basic rules.
> > Example: if every paths start with
> > 	drivers/crypto/
> > 	or lib/librte_cryptodev/
> > 	or doc/guides/cryptodevs/
> > 	then it goes to dpdk-next-crypto
> >
> > Later it would be a good idea to store the rules in the dpdk repo near
> > the file MAINTAINERS, so patchwork could parse them and display the
> > maintainers and the tree for the patches.
> >
> >
> > > > -----Original Message-----
> > > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > > > Sent: Thursday, April 6, 2017 7:46 PM
> > > >
> > > > 2017-04-06 09:57, Xu, Qian Q:
> > > > > As to the per patchset performance test, as you know, there are
> > > > > many repos
> > > > for DPDK now, so when a new patchset coming, which repo should it go to?
> > > > Maybe it doesn't go to dpdk master, but go to dpdk-next-virtio, or
> > > > others, but automation tool doesn't know that.
> > > > > As to per patch build, we are trying the patch on different repo
> > > > > to find the one
> > > > that can pass build, but as to performance test for per patchset,
> > > > we must apply the patchset into correct repo/branch or else the
> > > > code didn't
> > work.
> > > > > Any comments here?
> > > >
> > > > For most of the patches it should be obvious to determine the targetted
> repo.
> > > > We should add a script in dpdk-ci to get the repo name from a patchset.
> > > > Anyway, this technical discussion should be on ci at dpdk.org.
> >