+1 for deprecating Ruby Runtime if it's done via the JEP process. Although it may be important for users, I see no way to maintain that. To soften the impact we could make Ruby plugins available via a separate small update center so that users can install them (at their own risk).
Once/if JEP is accepted, heads-up announcement in the Blog Post may be also reasonable. It would allow to get attention from contributors and users who may want to contribute to migrating/replacing the plugins. Some plugins already have equivalent features offered by existing plugins, and such blog post could also pave the migration path. Gitlab Hook plugin is a problem for sure, but it's not that big in the terms of code from what I see. Maybe we could reach out to the vendor and ask whether they are interested to work on the port to Java. Best regards, Oleg On Monday, May 14, 2018 at 5:37:41 PM UTC+2, Jesse Glick wrote: > > On Mon, May 14, 2018 at 10:04 AM, Daniel Beck <[email protected] > <javascript:>> wrote: > > ruby-runtime has caused quite some work for core maintainers > > I have personally spent a fair amount of time trying to deal with it; > for example, writing what seems to have been the first acceptance test > exercising any Ruby-based functionality, so as to demonstrate the > effectiveness of a core workaround for a bug in this runtime. > > > WDYT? > > +1. From the perspective of Essentials I think we need to be willing > to sacrifice some old stuff which was serving as a drag on > productivity. For the case of GitLab hooks in particular, developer > effort would be better spent enhancing the (Java-based) branch source > plugin to react to SCM events without polling. > > I suppose this proposal would be best formalized as a “standards” JEP, > though JEP-1 does not specifically mention feature or subsystem > deprecation as a use case. > -- 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/3ac4642d-cee1-4b02-85d7-ef4d1d2d2aca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
