From: Thomas Monjalon <thomas@monjalon.net>
To: Patrick Robb <probb@iol.unh.edu>
Cc: ci@dpdk.org, alialnu@nvidia.com, Adam Hassick <ahassick@iol.unh.edu>
Subject: Re: DPDK clone/fetch URL
Date: Mon, 27 Nov 2023 21:58:31 +0100 [thread overview]
Message-ID: <5770736.7s5MMGUR32@thomas> (raw)
In-Reply-To: <CAJvnSUBQoey_KFxWj=Ae433EP0KySXJJHPcyL0JzO06eeBnZAg@mail.gmail.com>
27/11/2023 17:09, Patrick Robb:
> 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.
We should mirror next-* trees as well I think, good point.
> 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.
next prev parent reply other threads:[~2023-11-27 20:58 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
2023-11-27 20:58 ` Thomas Monjalon [this message]
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=5770736.7s5MMGUR32@thomas \
--to=thomas@monjalon.net \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
/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).