From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 8AA4F201; Thu, 8 Nov 2018 09:14:45 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1831121FB7; Thu, 8 Nov 2018 03:14:45 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 08 Nov 2018 03:14:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=fKrw9egVUc+v+fuVALDrBJU/MX60LuAAjhwhN10iOJw=; b=VP9TEJcS55SN 3y4JUyEjjEfyk6xSV56hhEpEXmuDbZL/jUVpfggzGVyHCMaeHfei/WK+POX/fuh5 JQCGTdSHrDYbPPpr+DYJEQoYArTAFMYErcsL/t6wlUnaGzsIWgiV65AxMXOlewDp rXO0WO2rEhPCJIkG6I/gMQ7hzcsCSIo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=fKrw9egVUc+v+fuVALDrBJU/MX60LuAAjhwhN10iO Jw=; b=XWd5n4N2H44Y4W/y94rvuJ1TQKGfisD4GEd5UOQ6H8QDPiEqgBABQRWW8 kCaujVzJ+jdD8YSAxNwsVctCaxNfoldF5i3XmAkSOIwjuZsZJsht4PAkkqG5Zi1k dB1UqJdxNikNz0eF3lvIIS+9jyKV23KVX4zkh224563nbO6JrDSF+BFj3BQiDL2f ESLfQKHJRBynwZJ7kvp/ExrY5zATd2hjahsPxOX88lSw63Ct9Zr+VkIzfEdYqo/F dm31EssY8rbV4+/hRiRUYFd4XSoFibjlerCXHKOSt2/t1ss3RHa6z6JlgWE6/5TP kujZ3rAAAgt0YyWJ35foSY2X8SLMA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 83E33E4430; Thu, 8 Nov 2018 03:14:43 -0500 (EST) From: Thomas Monjalon To: ci@dpdk.org Cc: Ali Alnubani , lijuan.tu@intel.com, tim.odriscoll@intel.com, web@dpdk.org Date: Thu, 08 Nov 2018 09:14:41 +0100 Message-ID: <3354634.DNSllWXiY1@xps> In-Reply-To: <20181108074622.5215-1-alialnu@mellanox.com> References: <20181108074622.5215-1-alialnu@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] [PATCH] add a link to the CI dashboard X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2018 08:14:45 -0000 Note: such patch must be sent to web@dpdk.org. 08/11/2018 08:46, Ali Alnubani: > --- a/content/perf-lab/_index.md > +++ b/content/perf-lab/_index.md > @@ -3,6 +3,10 @@ title = "Performance Lab" > weight = "8" > +++ > > +
> + {{< button href="https://lab.dpdk.org" >}} CI Dashboard {{< /button >}} > +
It is important to keep in mind that we support a distributed CI approach. This lab is an important part of the CI, but we can run other tests in other labs. That's why I think we must really stick with a specific name for this lab. Several names were mentionned so far: - performance lab - UNH lab - reference lab - community lab I think we must decide which name we want to use. Opinions?