From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 842AF43412; Thu, 30 Nov 2023 18:42:18 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7D4C840277; Thu, 30 Nov 2023 18:42:18 +0100 (CET) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id 3232D40266 for ; Thu, 30 Nov 2023 18:42:17 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id A351E32001BB; Thu, 30 Nov 2023 12:42:13 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 30 Nov 2023 12:42:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1701366133; x=1701452533; bh=BRIT6jYl/RQ27VUr5g+OFn2frdGYB+mRdxm I23AE/Zw=; b=rUViMCBEq1k+W69wUu3oyv0k1OoVjQMfm/RFXvBh+2HwXTl7Z2K JmIc0qhEY1hc/pvevuVSFmB8mxp+srhekkhlHArfm5IKEgabvfrRH0bYVmnt8TNG KEIympBaE0BoPgCj7ICXAIAjn0dZrTNqmd3IjXm6ZPoyWMS7ADpmZ0gFaSTZozPR MY/DWFsElrEhqbJ6J1EKvFFdHtaVvXFzU+dHTBM11NnGpKgDmnjF/FqMs4Hk5koY JTCRCjRgI9vlkQme5krh8JUK8hniF4yss9chlkBJCUGf+mSNsOc4pgpf527PIo0U 4128EnOFCltRaer9SOm83TW3hOAJQnqvwaQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1701366133; x=1701452533; bh=BRIT6jYl/RQ27VUr5g+OFn2frdGYB+mRdxm I23AE/Zw=; b=fC3aTqGYKzifqmULHJy4TMxbNrdNHJ+O3vMSw1q8Ol0FyGt6hz8 QI2VPqsAsOx5/NFIr6LmDCWxT9txUt0UZHYzlMcfarDOVhYMEyVHO2OSSJr8nGoX 47uqlBG0uF5SwhzlRdCOEglw9VtwyJ8L9KBz5fFv/TBhr4EQdQaBEKVnewWuGC3+ 3eapPoj61eJ89jZYANSV5EOYM4khp8SIs5G9Vj9Zwz4DCsit7w9s9c1zqIs2SB/h PN6BFQjWSZzL9I5NCRHwefGmGYifI3WoDSYPvsvWVtRhQC+31EIwkAxq3fvYPHVA eaEXzz+6sJffS0hcew67ASC0f7NTTVK6ohQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudeijedguddtfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnhepvddukeelfeeigfegueduffdvueffhfetvdeigfevjeeviedt gefhteffheffteejnecuffhomhgrihhnpeguphgukhdrohhrghdpohhrghdrrghspdhpfi gpmhgrihhnthgrihhnvghrshgptghlihdrphihnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 30 Nov 2023 12:42:11 -0500 (EST) From: Thomas Monjalon To: Adam Hassick , Patrick Robb , David Marchand Cc: ci@dpdk.org, alialnu@nvidia.com Subject: Re: DPDK clone/fetch URL Date: Thu, 30 Nov 2023 18:42:09 +0100 Message-ID: <24158151.0c2gjJ1VT2@thomas> In-Reply-To: References: <5933180.BEx9A2HvPv@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org 30/11/2023 10:27, David Marchand: > On Mon, Nov 27, 2023 at 10:30=E2=80=AFPM Adam Hassick wrote: > > Yes, mirroring the next-* branches would help to reduce the complexity = of creating patch series artifacts. > > As Patrick wrote, moving the clones for the periodic testing on DPDK ma= in and DPDK LTS should be a trivial change. > > > > However, most of the load we put on that server originates from our tes= ting on new patch series. > > I am working on a new script for creating the tarball artifacts from in= coming patch series. It only pulls down either 1 or 2 repositories rather t= han main and all next-* branches for every single patch. > > Once deployed, I expect this script to reduce the load on git.dpdk.org = significantly. > > Also, I anticipate that I can modify this new script to pull main down = from GitHub. Then, only incoming patch series for next-* branches will prod= uce any load on git.dpdk.org. >=20 > As mentionned in > https://inbox.dpdk.org/dev/CAJFAV8xSVqkTjrqSL0gWkg9Y+EyMg4=3DjxwOOzhtaXp6= HDeG_cQ@mail.gmail.com/T/#t, > the mirroring script is ready on dpdk.org. > The branches are not up yet, I'll put some update in this thread when the= y are. The branches are automatically created on GitHub when there is a push to the corresponding branch on dpdk.org. Some branches are already created on GitHub. When testing a patch, you should get a repository name from the script pw_maintainers_cli.py: https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py We could work on this script to get the GitHub branch name. =46or example, instead of git://dpdk.org/next/dpdk-next-net it should be the GitHub branch name next-net-for-main-repo. The branch name is the dpdk.org repository name without "dpdk-" followed by the default branch of the repository on dpdk.org. This is the list of branches to use on GitHub for patch testing: dpdk/main dpdk/next-baseband-for-main dpdk/next-crypto-for-main dpdk/next-eventdev-for-main dpdk/next-net-for-main-repo dpdk/next-net-brcm-for-next-net dpdk/next-net-intel-for-next-net dpdk/next-net-mlx-for-next-net dpdk/next-net-mrvl-for-main dpdk/next-virtio-for-next-net In addition, we will have some "useless" branches: dpdk/next-net-main dpdk/next-net-brcm-main dpdk/next-net-brcm-pre-submit dpdk/next-net-intel-main dpdk/next-net-mlx-main dpdk/next-virtio-staging dpdk/next-baseband-staging No automatic test should be run on these branches. And these are the branches that we should test on each push: dpdk-stable/21.11-staging dpdk-stable/22.11-staging dpdk-stable/23.11-staging (to be created) Note: we could discuss later about merging dpdk and dpdk-stable in the same GitHub repository.