-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.46.1
Groovy-Plugin 2.0
Windows host
Since the update to Groovy-Plugin 2.0, the edit field for specifying a classpath is missing in the build step "Execute system groovy script" when running a groovy script file.
I do understand, why you removed this feature (security), but now my scripts don't work any more, because they don't find the imported groovy classes any more.
Is there a better way for achieving a similiar functionality like specifying a classpath? Or is it possible to specify it in another way? Or do I have to change my scripts? If it is the latter one: how do I have to change them without adding new security risks?
In case there is no recommended solution or a workaround, we have to downgrade the Groovy-Plugin.