Thanks for resurrecting this! > On 14. Apr 2021, at 18:34, 'Gavin Mogan' via Jenkins Developers > <[email protected]> wrote: > > I saw ruby runtime being no longer supported in core but I can't find > confirmation of that, so may have been thinking of this discussion.
https://github.com/jenkinsci/jenkins/blob/6f2e7b0085e39d02a92312a57a5cf7f0b84dfc05/core/src/main/resources/jenkins/security/whitelisted-classes.txt#L172-L198 is still in and can be cleaned up once we decide to go forward (I think this is one of the changes the JEP refers to). > So revisiting, Can we suspend distribution of these plugins now? take them > out of update center, prevent new installs from happening. As stated in the > earlier comments by Jesse, this wouldn't prevent existing installs from using > them (although they probably don't work), but would prevent peoples installs > from getting worse. > > If the only blocker to doing so was writing up a blog post I can draft > something and we can start the process of removing the support and plugins > for ruby runtime Since the last time we discussed this (and I created the JEP), we added deprecation warning support to Jenkins 2.246 and newer, which is basically designed for such a case. This makes JEP-7 much cleaner to implement, because we now have good ways to inform users about it. I'd start with a deprecation warning for ruby-runtime and all dependent plugins pointing to the JEP or this thread (or, if you want to write it up, a blog post), and if folks don't <s>complain</s> offer to take over ruby-runtime maintainership in large enough numbers, we can suspend a few weeks later, followed by core cleanup. WDYT? -- 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/C7E64F3D-4763-433D-928D-F3CC2FA631C3%40beckweb.net.
