DPDK clone/fetch URL

[David Marchand]

Hello guys,

On Mon, Nov 27, 2023 at 10:30 PM Adam Hassick <ahassick at iol.unh.edu> 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 testing on new patch series.
> I am working on a new script for creating the tarball artifacts from incoming patch series. It only pulls down either 1 or 2 repositories rather than 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 produce any load on git.dpdk.org.

As mentionned in
https://inbox.dpdk.org/dev/CAJFAV8xSVqkTjrqSL0gWkg9Y+EyMg4=jxwOOzhtaXp6HDeG_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.


-- 
David Marchand