DPDK clone/fetch URL

[Thomas Monjalon]

30/11/2023 10:27, David Marchand:
> On Mon, Nov 27, 2023 at 10:30 PM Adam Hassick <ahassick at iol.unh.edu> 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 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.

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.
For 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.