DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org, alialnu@nvidia.com, Adam Hassick <ahassick@iol.unh.edu>
Subject: Re: DPDK clone/fetch URL
Date: Mon, 27 Nov 2023 11:09:51 -0500	[thread overview]
Message-ID: <CAJvnSUBQoey_KFxWj=Ae433EP0KySXJJHPcyL0JzO06eeBnZAg@mail.gmail.com> (raw)
In-Reply-To: <5933180.BEx9A2HvPv@thomas>

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

Hello,

Thanks for the heads up Thomas. For the Community Lab, as far as I can
tell, every git clone/fetch for DPDK main and DPDK LTS should be able to be
moved to the GitHub repo.

On the other hand, I don't think next-* branches are mirrored on GitHub (at
least for now), so unless I'm mistaken, we will still have to pull from
git.dpdk.org. But, between DPDK main and LTS, it should still be a sizable
reduction on the load put on your server. I'll discuss with the team today
and we will update here.

Best,
Patrick


On Mon, Nov 27, 2023 at 6:21 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> Hello,
>
> The server git.dpdk.org is not strong enough to hold all CI requests.
> When a script is doing a git fetch or clone, it is consuming workload on
> the server.
> Please could you favor the mirror on GitHub in any CI automation?
>         https://github.com/DPDK/dpdk.git
> This mirror is updated as frequently as git.dpdk.org:
> We push to git.dpdk.org where a git hook is replicating the same on
> GitHub.
>
> Hope we can reduce the workload on our main server.
> Thank you everyone for collaborating.
>
>
>

-- 

Patrick Robb

Technical Service Manager

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

www.iol.unh.edu

[-- Attachment #2: Type: text/html, Size: 3931 bytes --]

  reply	other threads:[~2023-11-27 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 11:20 Thomas Monjalon
2023-11-27 16:09 ` Patrick Robb [this message]
2023-11-27 20:58   ` Thomas Monjalon
2023-11-27 21:32     ` Adam Hassick
2023-11-28 21:16       ` Patrick Robb
2023-11-30  9:27       ` David Marchand
2023-11-30 17:42         ` Thomas Monjalon
2023-11-30 15:57 ` Aaron Conole

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='CAJvnSUBQoey_KFxWj=Ae433EP0KySXJJHPcyL0JzO06eeBnZAg@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=ahassick@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).