Personally I am +1 about **considering** it. My main concern is that Groovy logic is being often [mis]used by configuration management tools, e.g. to install plugins by CLI calls. If we remove CLI handlers from the core, I would expect it to cause some collateral damage on this scenarios. IMHO it needs a wider poll via Users mailing list and blog post once CI is accepted as a draft.
Regarding keeping Groovy in the core, we need a pluggable core components story (JENKINS-41196 <https://issues.jenkins-ci.org/browse/JENKINS-41196>) to be delivered for that. Groovy Init Hooks are critical to Jenkins environments, and this part should not be detached to plugins IMHO. BR, Oleg понедельник, 13 ноября 2017 г., 17:52:06 UTC+1 пользователь Daniel Beck написал: > > > > On 13. Nov 2017, at 17:40, R. Tyler Croy <ty...@monkeypox.org > <javascript:>> wrote: > > > > What impact does this have on the Script Console or the CLI, both of > which > > expose scripting functionality? > > The "Script Console" and groovy/groovysh CLI commands (and more) would be > moved into a plugin, so OOTB, Jenkins would have no text fields taking > 'system' Groovy for management purposes. > > The idea is that with that plugin, the exact same features will be > available, but without it, you don't have them. Implementation TBD. > > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/80102361-9d82-43da-b254-e85909d7a238%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
