From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, ci@dpdk.org
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>,
Jeremy Plsek <jplsek@iol.unh.edu>
Subject: Re: [dpdk-ci] bugzilla section for the lab
Date: Tue, 21 Aug 2018 13:31:11 +0100 [thread overview]
Message-ID: <7e4b37f2-dda8-7e2f-e377-b445f6961655@intel.com> (raw)
In-Reply-To: <2274547.mcss5qQXk0@xps>
On 8/20/2018 6:16 PM, Thomas Monjalon wrote:
> Hi,
> Following up on below request:
>
> 01/08/2018 15:55, O'Driscoll, Tim:
>> * Thomas will update Bugzilla so we can use it for tracking lab tickets.
>
> I have created a new "product" in bugzilla, called "lab".
> Now we can fill a bug for the lab:
> https://bugs.dpdk.org/enter_bug.cgi
>
> Then you can choose between "dashboard" and "UNH infra".
> If we need other or more bugzilla components, please ask.
Is only for defects, when implementation doesn't match the requirement, or do we
plan to use bugzilla for new requirements and/or changing existing requirements?
>
> The default assignee, for above components, is ci@dpdk.org
> mailing list, meaning that new bugs will be posted here.
> Jeremy is already on the default Cc list.
> If you think the Cc list must be modified, please ask.
>
> I think we can use this bugzilla section for other labs
> participating in the distributed CI (Intel for now).
> It would require to create just a new "component" in bugzilla.
>
> Hope it will be useful
>
>
next prev parent reply other threads:[~2018-08-21 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 13:55 [dpdk-ci] Minutes of DPDK Lab Meeting, July 31st O'Driscoll, Tim
2018-08-20 17:16 ` [dpdk-ci] bugzilla section for the lab Thomas Monjalon
2018-08-21 12:31 ` Ferruh Yigit [this message]
2018-08-21 17:22 ` Jeremy Plsek
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=7e4b37f2-dda8-7e2f-e377-b445f6961655@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ci@dpdk.org \
--cc=jplsek@iol.unh.edu \
--cc=tdelanerolle@linuxfoundation.org \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
/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).