Controllers would make more sense, I don't think I have enough knowledge about the agents
'Bruno Verachten' via Jenkins Developers <[email protected]> schrieb am Di., 4. Feb. 2025, 19:05: > I thought I had understood you were targeting all the other controllers in > the same network, not the agents. 🤔 > > On Tue, Feb 4, 2025, 18:58 Alex Earl <[email protected]> wrote: > >> My understanding is that agents do not download plugins at all, the >> plugins only reside on the controller. >> >> On Tue, Feb 4, 2025 at 10:56 AM Phillipp Glanz <[email protected]> >> wrote: >> >>> 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 [email protected] >>> 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 <[email protected]> >>>> 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 [email protected]. >>> To view this discussion visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/0752cb85-326e-4052-9ec5-cda97837d167n%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/0752cb85-326e-4052-9ec5-cda97837d167n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> 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 [email protected]. >> To view this discussion visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcd%3DNAfULhock2%2B6FVSj4-9fusnAA_tWxqLdeHS_M4kFQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcd%3DNAfULhock2%2B6FVSj4-9fusnAA_tWxqLdeHS_M4kFQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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 [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAFbR2roD4hCo%2BrddCNebj9ecGU6%2BEup3xMzhGwHeyRe8k0hbNA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAFbR2roD4hCo%2BrddCNebj9ecGU6%2BEup3xMzhGwHeyRe8k0hbNA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CALSuxiutQGpZFy5xifn2YZA1XEuBSa0_nFXBd3Y%3DoBzW%2BqZXQg%40mail.gmail.com.
