From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, jplsek@iol.unh.edu
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] bugzilla categories
Date: Wed, 13 Feb 2019 12:02:59 +0000 [thread overview]
Message-ID: <2509b54c-7b38-d724-a566-3f5e990fe5cd@intel.com> (raw)
In-Reply-To: <3216607.B7dzNUL3zR@xps>
On 2/12/2019 5:44 PM, Thomas Monjalon wrote:
> Hi,
>
> In bugzilla, for the product "lab", we have 3 components:
> - dashboard
> - job scripts
> - UNH infra
> see https://bugs.dpdk.org/describecomponents.cgi?product=lab
>
> I think it is clear what dashboard (HTML page)
> and UNH infra (servers management) are.
>
> It is a bit less clear for "job scripts".
> We need to add a lot of scripting tasks for running the tests.
> Should we split this category in 2:
> - job scripts for specific behaviour and selection of tests
> - CI scripts for generic scripts to be hosted in dpdk-ci.git
>
> For instance, the scripts for parsing patches, applying patches,
> generating reports and interfacing with patchwork
> could be shared on http://git.dpdk.org/tools/dpdk-ci/
> and may deserve a new category "CI scripts".
>
> Opinions?
+1 to "CI scripts" category.
prev parent reply other threads:[~2019-02-13 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 17:44 Thomas Monjalon
2019-02-13 12:02 ` Ferruh Yigit [this message]
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=2509b54c-7b38-d724-a566-3f5e990fe5cd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ci@dpdk.org \
--cc=jplsek@iol.unh.edu \
--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).