From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 843F6695D for ; Tue, 12 Feb 2019 18:44:13 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0A7BC2207F; Tue, 12 Feb 2019 12:44:13 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 12 Feb 2019 12:44:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding:content-type; s=mesmtp; bh=QUZ2ZcMs2G L45bNLFfWaMT3QNm9FLerPAJEHWFngCMs=; b=bub0TRHijXONZGIKP6EVRlC+xQ pHsR8fUF0xrrF9AlwJbEmtVQCRMs1oghKDpCFO4T102j/QS0tkaI//TKSbEiM/24 SNXcpROyAdfFT5b5l5LtfxZGw+CBdb1y77DD5xN8NdeHMcVE6dE/1LfTqumeMGYT DcgUsqsDgKFK779gs= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=QUZ2Zc Ms2GL45bNLFfWaMT3QNm9FLerPAJEHWFngCMs=; b=vQsxtEiU/BonTbFx5u1LTf phy3b3osgtYuV+/xXBDHqi2lXVNoLh+OFVjYKufi3hQ7YOxiemQPLQ4c0w/+8jsk aPOrFy3fNbw/JOAm70yLTYpiit3OMqME6vyjBZiLzkN2YDAiUP/B+0HLaMUEFBgy hHgW962CYaNCuFD6NHudnXF0FIDj3n1oOv1ugFCrn4F9EPwtz0/8lSRXADgcER9G t86Q8yGnymoNH6FJrqV3GhPhSXkfmj2jgv2al9qG/3ZqkzN7WCVG5/Vyh0mkGSyd JxVZg73hMpq3DvuOAzRS0LWiOaoXJkQ2m7zpnT4Qoz4FrVSmMpsC42Vhep2ub/cg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledruddtuddguddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucenucfjughrpefhvffufffkggfgtgesthfuredttddtvdenucfhrhhomhepvf hhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvght qeenucffohhmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvddtfedrud ekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdr nhgvthenucevlhhushhtvghrufhiiigvpedt 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 E782C10315; Tue, 12 Feb 2019 12:44:11 -0500 (EST) From: Thomas Monjalon To: jplsek@iol.unh.edu Cc: ferruh.yigit@intel.com, ci@dpdk.org Date: Tue, 12 Feb 2019 18:44:09 +0100 Message-ID: <3216607.B7dzNUL3zR@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-ci] bugzilla categories X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2019 17:44:13 -0000 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?