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 22F5C4340F; Thu, 30 Nov 2023 10:27:49 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0260042E97; Thu, 30 Nov 2023 10:27:49 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 15CA942E94 for ; Thu, 30 Nov 2023 10:27:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1701336466; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hj7zMDdKBJffuuGQZwze+wYt5U6YjYmEJz3RmqHl7i8=; b=fEf425wr4btVL5g/fPYdAO6M5QkI9nLhpN6SqUNNR/QbZVRiUxMu/ml47UtL2JbjnekQ4P 9xb7e0ArJQ7dcPJjs84xFbwSaWzpiyLpgiri7o4zOb/TdU2xEAXhNtwZ0hhrTGyvtQ0HK9 LPIxRm/gUQlqpeZGTZgtLsi3smitT7w= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-82-XzaifYueMN-6T7NIIg3ntQ-1; Thu, 30 Nov 2023 04:27:44 -0500 X-MC-Unique: XzaifYueMN-6T7NIIg3ntQ-1 Received: by mail-lj1-f197.google.com with SMTP id 38308e7fff4ca-2c9c3782740so8181021fa.2 for ; Thu, 30 Nov 2023 01:27:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701336463; x=1701941263; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=hj7zMDdKBJffuuGQZwze+wYt5U6YjYmEJz3RmqHl7i8=; b=dm4v/iycATOcISY60g/gez8ILSI2pXP4ig4beYH6vKC60dN2e9tikbRkw6j6ZQWND5 +78/AC36Ju1JuHS3eyex2Fa99MTBY9GZ+roAVo5+WvJJILCvTSi7TniSl4WcZMCMekk9 OrBGE1bTwk+iCCIaOqE+s+HZE2kcUUA4PHC19S5c0cI18rOyvU2wYFGvecTNJfxQIhIn nFpwoxvCmOK776fJw9nkZ/5wJHzX67F04YSE+dAGCJC6wogfJ/dbOqa9q0MtaPGpgFjr j0vdtEcr66G7zQxi4lDqcgJrveuQAYwTPI+qDgLIeWHrA5HfV/69bO3DMtcNeBdL7Csl eRYA== X-Gm-Message-State: AOJu0YwOr1fqYmTmYwZt/ushsibCjYLmAcqeV0wMCyqE09QlGVJOF4il +BIsFkCsI/paIlsSi44pLtrLb4vFh0+0mcEZbB9C7F/An1hJ0isYwN9ICjKaIavUu6HDA5oeLQS z50Gm4x07fieu6GB2Dg== X-Received: by 2002:a2e:904e:0:b0:2c9:b952:ab42 with SMTP id n14-20020a2e904e000000b002c9b952ab42mr4171023ljg.50.1701336462984; Thu, 30 Nov 2023 01:27:42 -0800 (PST) X-Google-Smtp-Source: AGHT+IHTV+39KjoR9TmDDVdhi+3qVUa9ErIquNH130p3orw0omIOanFYRhX1ApH2dkQD7g2fohBkR45a/59hKAKZtwc= X-Received: by 2002:a2e:904e:0:b0:2c9:b952:ab42 with SMTP id n14-20020a2e904e000000b002c9b952ab42mr4170998ljg.50.1701336462683; Thu, 30 Nov 2023 01:27:42 -0800 (PST) MIME-Version: 1.0 References: <5933180.BEx9A2HvPv@thomas> <5770736.7s5MMGUR32@thomas> In-Reply-To: From: David Marchand Date: Thu, 30 Nov 2023 10:27:31 +0100 Message-ID: Subject: Re: DPDK clone/fetch URL To: Adam Hassick , Patrick Robb Cc: Thomas Monjalon , ci@dpdk.org, alialnu@nvidia.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Hello guys, On Mon, Nov 27, 2023 at 10:30=E2=80=AFPM Adam Hassick wrote: > > Hi Thomas, > > 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 main= and DPDK LTS should be a trivial change. > > However, most of the load we put on that server originates from our testi= ng on new patch series. > I am working on a new script for creating the tarball artifacts from inco= ming patch series. It only pulls down either 1 or 2 repositories rather tha= n main and all next-* branches for every single patch. > Once deployed, I expect this script to reduce the load on git.dpdk.org si= gnificantly. > Also, I anticipate that I can modify this new script to pull main down fr= om GitHub. Then, only incoming patch series for next-* branches will produc= e any load on git.dpdk.org. As mentionned in https://inbox.dpdk.org/dev/CAJFAV8xSVqkTjrqSL0gWkg9Y+EyMg4=3DjxwOOzhtaXp6HD= eG_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 they = are. --=20 David Marchand