Re: JEP proposal: Removing user-facing scripting features from core

2017-11-14 Thread Jesse Glick
On Mon, Nov 13, 2017 at 11:34 PM, Kohsuke Kawaguchi wrote: > Is this any different from all the other extractions of features into > plugins? I guess back then we used to bundle those extracted stuff as > bundled plugins? We now bundle them in `jenkins.war` as _detached_

Re: JEP proposal: Removing user-facing scripting features from core

2017-11-13 Thread Kohsuke Kawaguchi
Is this any different from all the other extractions of features into plugins? I guess back then we used to bundle those extracted stuff as bundled plugins? On Tue, Nov 14, 2017 at 4:30 AM Jesse Glick wrote: > On Mon, Nov 13, 2017 at 6:25 AM, Daniel Beck

Re: JEP proposal: Removing user-facing scripting features from core

2017-11-13 Thread Jesse Glick
On Mon, Nov 13, 2017 at 6:25 AM, Daniel Beck wrote: > Would https://github.com/jenkinsci/jenkins/pull/3006 (the goal, rationale > etc., not the implementation details) have a chance as a JEP Yes. -- You received this message because you are subscribed to the Google Groups

Re: JEP proposal: Removing user-facing scripting features from core

2017-11-13 Thread Oleg Nenashev
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

Re: JEP proposal: Removing user-facing scripting features from core

2017-11-13 Thread Daniel Beck
> On 13. Nov 2017, at 17:40, R. Tyler Croy 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,

Re: JEP proposal: Removing user-facing scripting features from core

2017-11-13 Thread R. Tyler Croy
(replies inline) On Mon, 13 Nov 2017, Daniel Beck wrote: > Hi everyone, > > This is a pre-JEP check[1]: Would > https://github.com/jenkinsci/jenkins/pull/3006 (the goal, rationale etc., not > the implementation details) have a chance as a JEP, or is it a waste of time? What impact does this

JEP proposal: Removing user-facing scripting features from core

2017-11-13 Thread Daniel Beck
Hi everyone, This is a pre-JEP check[1]: Would https://github.com/jenkinsci/jenkins/pull/3006 (the goal, rationale etc., not the implementation details) have a chance as a JEP, or is it a waste of time? Thanks, Daniel 1: https://github.com/jenkinsci/jep/tree/master/jep/1#discussion -- You