<div dir="ltr"><div dir="ltr"><div><div><div><div>Hi Thomas,<br><br></div>Yes, mirroring the next-* branches would help to reduce the complexity of creating patch series artifacts.<br>As Patrick wrote, moving the clones for the periodic testing on DPDK main and DPDK LTS should be a trivial change.<br><br></div>However, most of the load we put on that server originates from our testing on new patch series.<br>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.<br>Once deployed, I expect this script to reduce the load on <a href="http://git.dpdk.org">git.dpdk.org</a> significantly.<br>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 <a href="http://git.dpdk.org">git.dpdk.org</a>.<br></div><div><br></div>Thanks,<br></div>Adam Hassick<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 27, 2023 at 3:58 PM Thomas Monjalon <<a href="mailto:thomas@monjalon.net">thomas@monjalon.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">27/11/2023 17:09, Patrick Robb:<br>
> Hello,<br>
> <br>
> Thanks for the heads up Thomas. For the Community Lab, as far as I can<br>
> tell, every git clone/fetch for DPDK main and DPDK LTS should be able to be<br>
> moved to the GitHub repo.<br>
> <br>
> On the other hand, I don't think next-* branches are mirrored on GitHub (at<br>
> least for now), so unless I'm mistaken, we will still have to pull from<br>
> <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a>. But, between DPDK main and LTS, it should still be a sizable<br>
> reduction on the load put on your server. I'll discuss with the team today<br>
> and we will update here.<br>
<br>
We should mirror next-* trees as well I think, good point.<br>
<br>
<br>
> On Mon, Nov 27, 2023 at 6:21 AM Thomas Monjalon <<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>> wrote:<br>
> <br>
> > Hello,<br>
> ><br>
> > The server <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a> is not strong enough to hold all CI requests.<br>
> > When a script is doing a git fetch or clone, it is consuming workload on<br>
> > the server.<br>
> > Please could you favor the mirror on GitHub in any CI automation?<br>
> > <a href="https://github.com/DPDK/dpdk.git" rel="noreferrer" target="_blank">https://github.com/DPDK/dpdk.git</a><br>
> > This mirror is updated as frequently as <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a>:<br>
> > We push to <a href="http://git.dpdk.org" rel="noreferrer" target="_blank">git.dpdk.org</a> where a git hook is replicating the same on<br>
> > GitHub.<br>
> ><br>
> > Hope we can reduce the workload on our main server.<br>
> > Thank you everyone for collaborating.<br>
<br>
<br>
<br>
</blockquote></div></div>