To explain the point better, If you have a controller node and multiple agents, the current flow seems to be that after a plugin install. All nodes download the plugins directly from jenkins.io. From my point of view, it would make more sense to get them from the controller node if this node already has the plugin anyway. Provided the agent and controller versions are the same. This would at least greatly reduce the traffic that goes outside and calls jenkins.io from the agents
On Monday, February 3, 2025 at 5:38:34 PM UTC+1 m...@basilcrow.com wrote: > What would be the consumer(s) of this cache? Other controller(s) in > the same network? The generic caching functionality of something like > Artifactory might be a better fit for this use case. > > On Mon, Feb 3, 2025 at 1:26 AM Phillipp Glanz <meinerl...@gmail.com> > wrote: > > > > Hi everyone, > > my name is Phillipp, I was at the Contributor Summit in Brussels on > Friday, January 31st. During the presentation of the monthly traffic > figures for Cloudflare, I had the idea of using the controller node as a > cache for plugin downloads within the network. This could reduce latency or > traffik to jenkins infrastructure. I would like to get feedback on my > suggestion. > > > > Regards > > Phillipp / TheMeinerLP > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/0752cb85-326e-4052-9ec5-cda97837d167n%40googlegroups.com.
