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.