DPDK CI discussions
 help / color / Atom feed
From: Jeremy Plsek <jplsek@iol.unh.edu>
To: Ali Alnubani <alialnu@mellanox.com>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] [PATCH v4] add script to decide best tree match for patches
Date: Fri, 19 Apr 2019 12:21:09 -0400
Message-ID: <CA+xUZB7_z4_TWCdSTvSU63Y_TGurdQFUpgjJkYEYC3GCSGkKyQ@mail.gmail.com> (raw)
In-Reply-To: <AM6PR05MB4405DE8BD5E7C6F358BB538FD7260@AM6PR05MB4405.eurprd05.prod.outlook.com>

We've switched to using it a few days ago.
Some examples of it switching branches:
https://lab.dpdk.org/results/dashboard/patchsets/5503/
https://lab.dpdk.org/results/dashboard/patchsets/5499/
https://lab.dpdk.org/results/dashboard/patchsets/5498/

On Thu, Apr 18, 2019 at 4:16 AM Ali Alnubani <alialnu@mellanox.com> wrote:
>
> Hi,
>
> > -----Original Message-----
> > From: ci <ci-bounces@dpdk.org> On Behalf Of Ali Alnubani
> > Sent: Tuesday, April 9, 2019 7:13 PM
> > To: ci@dpdk.org
> > Cc: Thomas Monjalon <thomas@monjalon.net>; ferruh.yigit@intel.com;
> > jplsek@iol.unh.edu; Ori Kam <orika@mellanox.com>
> > Subject: [dpdk-ci] [PATCH v4] add script to decide best tree match for
> > patches
> >
> > The information provided in the MAINTAINERS file is used to find the tree
> > that matches the files changed in patches as follows:
> >  - For each file, it first tries to find a matching unix shell-style
> >    pattern. If one was found, it looks for a tree specified in the
> >    subsection containing the pattern, and that tree is returned.
> >    If no tree was found in that subsection, the script tries to
> >    find a tree specified under the name of the section containing
> >    the pattern.
> >  - If more than one tree was matched (for multiple files),
> >    a tree matching the common prefix of all these trees will be
> >    returned.
> >  - The main repo 'dpdk' will be returned if no other match was found.
> >
> > Results can be further improved by adding more information to the
> > MAINTAINERS file or by using the subject of the series/patch for matching
> > too.
> >
> > Bugzilla ID: 166
> >
> > Suggested-by: Thomas Monjalon <thomas@monjalon.net>
> > Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
> > Signed-off-by: Ori Kam <orika@mellanox.com>
> > ---
> > Changes in v2:
> Typo.
> s/v2/v4/
> >   - Refactored the script to use classes, which makes it easier
> >     to be used inside other scripts.
> >   - Renamed the script so that it can be imported.
> >   - The script will always return a single tree.
> >     If multiple trees were matched (for multiple files),
> >     a tree matching the common prefix of all these trees will be
> >     returned.
> >   - Main repo is now reported if no other matches were found.
> >   - Only tree name will be returned without the full url.
> >   - Updated description and usage info.
> >
>
> Did you guys get a chance to test this version?
>
> Thanks,
> Ali



-- 
Jeremy Plsek
UNH InterOperability Laboratory

  reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 14:48 [dpdk-ci] [PATCH v2] " Ali Alnubani
2019-02-15 21:28 ` Jeremy Plsek
2019-02-15 23:08   ` Thomas Monjalon
2019-02-17  8:09     ` Ali Alnubani
2019-02-16 16:03 ` [dpdk-ci] [PATCH v3] " Ali Alnubani
2019-04-09 16:12   ` [dpdk-ci] [PATCH v4] " Ali Alnubani
2019-04-18  8:16     ` Ali Alnubani
2019-04-19 16:21       ` Jeremy Plsek [this message]
2019-04-19 16:24         ` Thomas Monjalon
2019-04-19 17:33           ` Jeremy Plsek
2019-04-19 17:55             ` Thomas Monjalon
2019-04-19 18:06               ` Jeremy Plsek
2019-04-19 19:41                 ` Thomas Monjalon
2019-04-19 19:45                   ` Jeremy Plsek
2019-04-19 20:39     ` Thomas Monjalon

Reply instructions:

You may reply publically 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=CA+xUZB7_z4_TWCdSTvSU63Y_TGurdQFUpgjJkYEYC3GCSGkKyQ@mail.gmail.com \
    --to=jplsek@iol.unh.edu \
    --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

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