(replies inline) On Sun, 26 May 2019, Daniel Beck wrote:
> > > > On 17. May 2019, at 12:08, Francisco Javier Fernandez > > <[email protected]> wrote: > > > > I'm wondering if it's worth to change the default behaviour and disable it, > > so anyone who wants this feature enabled should use the > > hudson.DNSMultiCast.disabled system property. It does not seem to be a > > widely used feature. > > IIUC, the rationale for having these installed is for IT staff in large > organizations to be able to discover Jenkins instances on their network, > typically operated by developers wanting/needing to bypass red tape. > Identifying these services is the first step to improve > standardization/operations. > > For that reason, anything but core-bundled, enabled-by-default means the > feature might as well not exist. I think it's worth removing the feature. Frankly, if somebody needs multicast to find a Jenkins server on their network, then they should probably not be considerd IT/network admins. Finding a Jenkins instance in a big network is trivially easy, as cryptominers have demonstrated quite effectively over the past couple years ^_^ IMHO this is not a feature, but technical debt that's best removed. Cheers -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20190526171559.fhmtb63o7n66lbm6%40grape. For more options, visit https://groups.google.com/d/optout.
