> > 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. … once they upgrade. We're not deleting plugin HPIs or other data from > their local disks. > same as above BR, Oleg On Monday, August 13, 2018 at 10:07:59 PM UTC+2, Daniel Beck wrote: > > > > On 13. Aug 2018, at 01:59, Oleg Nenashev <[email protected] > <javascript:>> wrote: > > > > Sorry, I have missed my action item in this thread. I am really afraid > of the "it will take 15 minutes to implement the specification" statement. > Sure, it's just 15 minutes if we agree that approximately 5% of Jenkins > installations get seriously impacted by the change and lose critical > plugins without preliminary announcement. > > … once they upgrade. We're not deleting plugin HPIs or other data from > their local disks. > > > Just to clarify the request, I would expect the following... > > • Do you plan to create a blogpost announcing the change in > advance (e.g. 2 weeks before the plugins are removed)? > > No. Changelogs (and in the case of LTS, upgrade guides) inform users about > changes to Jenkins. > > > • Would you add some administrative warnings directly to the > Jenkins instances using plugins? Itcan be implemented via a security > announcement with existing tools AFAICT > > No, as the warnings UI is specifically labeled 'security'. > > > • Do you plan to notify plugin maintainers in advance so that > they have a chance to react before the plugins disappear from the main UC? > > As Jesse wrote, this thread and the JEP are the notification. > > > • Do you plan to offer workarounds so that users can keep using > the plugins for a while (e.g. by downloading from the experimental UC or > so)? > > The workaround is to not throw away what downloads they already have, or > especially savvy users can download from Artifactory -- similar to April > 2017 when we delisted numerous plugins. > > > One may say that it is enough to just announce a change in the weekly > changelog and then reference it in upgrade guidelines. I am not 100% sure > about that, because, should a security release happen at the same > timeframe, users may be dead in water if they depend on the main update > centers (not recommended for paranoid setups, I'd guess). > > OK, so we'll schedule the core change (the part I specifically excluded > from "15 minutes") to shortly _after_ a scheduled core security fix. Easy > enough to do. > > -- 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/fc0d1b3b-f1d9-46da-87e1-3df1419d7d84%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
