> On 16. Aug 2018, at 19:45, Oleg Nenashev <[email protected]> wrote: > >> You mean, so that _new_ users can _install_ the plugins? I would say no. > > How would you define a "new" user in the new configuration-as-code world? If > somebody uses official Jenkins Docker image with plugins.txt, the plugins > will fail to install when you rebuild the image after the change gets > deployed. And it is a pretty popular approach nowadays. Plugin installation > features in JCasC 1.0 RC would be also affected AFAICT.
As of last count, 111 installs of CasC plugin. I'd be _very_ surprised if this ended up affecting more than 5 systems total. And while this isn't the only approach to configuration-as-code, people should not expect us to continue distributing plugins indefinitely after we blacklisted the likes of Scriptler, Build Flow, Copy to Slave, or Perforce. Notably, update sites only have the newest release, which isn't suitable for C-as-C anyway, so I expect the more stable approaches to use our Maven repo anyway -- which will not be affected. Running one's own Maven repo has been an important best practice for a long time. With C-as-C, running one's own update site should be similar. I will amend the JEP to record this concern and the answers. I don't think we need to change anything about the chosen approach. -- 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/C1E30C7F-1CC2-4A33-853F-0568A9A818C4%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
