Re: PROPOSAL: Remove network discovery services

2020-01-31 Thread Matt Sicker
On Fri, Jan 31, 2020 at 3:35 AM Amit Dar wrote: > As a heavy Swarm Plugin user, I can say we don't use the discovery feature of > the plugin, but rather direct the client to a specific master. This is due > the fact we have several Jenkins masters in the same network (for testing > purposes,

Re: PROPOSAL: Remove network discovery services

2020-01-31 Thread Daniel Beck
We propose to remove these network discovery services. See https://issues.jenkins-ci.org/browse/JENKINS-60913 and https://github.com/jenkinsci/jenkins/pull/4460 . > Please respond with any agreement or if you have any important > implementations that require these capabilities. Perhaps if this is

Re: PROPOSAL: Remove network discovery services

2020-01-31 Thread Amit Dar
Hi, As a heavy Swarm Plugin user, I can say we don't use the discovery feature of the plugin, but rather direct the client to a specific master. This is due the fact we have several Jenkins masters in the same network (for testing purposes, mainly). I think the usage of the auto discovery

Re: PROPOSAL: Remove network discovery services

2020-01-31 Thread Ivan Fernandez Calvo
Swarm plugin has about 7000 installations, this is the potential Jenkins instances affected, I am agree to remove it from the core but I think that should be provided as a plugin, maybe the needed staff can be moved to the swarm plugin. -- You received this message because you are subscribed

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread Jeff Thompson
On 1/30/20 1:43 PM, Jesse Glick wrote: On Thu, Jan 30, 2020 at 1:41 PM Jeff Thompson wrote: I'd be willing to help get things going with that, but not to maintain it. If nobody is interested enough for that, we should kill it off. Fine with me. My perspective was that it sounded like little

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread Jeff Thompson
On 1/30/20 1:33 PM, Baptiste Mathus wrote: Le jeu. 30 janv. 2020 à 20:10, Tim Jacomb > a écrit : +1 on removing it, is there actually going to be anyone using it who is updating their Jenkins version? I.e is a plugin needed? Would it be worth and possible

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread Jesse Glick
On Thu, Jan 30, 2020 at 1:41 PM Jeff Thompson wrote: > I'd be willing to help get things going with that, but not to maintain it. If > nobody is interested enough for that, we should kill it off. Fine with me. My perspective was that it sounded like little additional effort to dump the

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread Baptiste Mathus
Le jeu. 30 janv. 2020 à 20:10, Tim Jacomb a écrit : > +1 on removing it, is there actually going to be anyone using it who is > updating their Jenkins version? I.e is a plugin needed? > Would it be worth and possible writing a jep-214 Telemetry impl to catch stats about this use? (Though it'd

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread Tim Jacomb
+1 on removing it, is there actually going to be anyone using it who is updating their Jenkins version? I.e is a plugin needed? On Thu, 30 Jan 2020 at 19:50, Slide wrote: > I'm +1 on this, reducing the attack footprint for core is a good idea. > > On Thu, Jan 30, 2020 at 11:41 AM Jeff Thompson

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread 'Gavin Mogan' via Jenkins Developers
I'm also very much a +1 to this It doesn't work inside of docker anyways, and yea less attack footprint the better. On Thu, Jan 30, 2020 at 10:50 AM Slide wrote: > I'm +1 on this, reducing the attack footprint for core is a good idea. > > On Thu, Jan 30, 2020 at 11:41 AM Jeff Thompson > wrote:

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread Jeff Thompson
On 1/30/20 11:25 AM, Jesse Glick wrote: On Thu, Jan 30, 2020 at 11:47 AM Jeff Thompson wrote: the capabilities could be pulled out of core into a plugin That was the longstanding proposal in JENKINS-33596. I think it's time to act on it. The key to implementing it in a plugin is to have

Re: PROPOSAL: Remove network discovery services

2020-01-30 Thread Jesse Glick
On Thu, Jan 30, 2020 at 11:47 AM Jeff Thompson wrote: > the capabilities could be pulled out of core into a plugin That was the longstanding proposal in JENKINS-33596. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

PROPOSAL: Remove network discovery services

2020-01-30 Thread Jeff Thompson
Hi, Dating back many years, Jenkins has supported two network discovery services (UDP multicast/broadcast and DNS multicast). When this was first implemented this may have been a reasonable way to provide useful lookup services. With modern Jenkins capabilities, networks, and security