I recognize the need for secure scripting sandboxes, but it seems as though 
the sandbox often excludes functions that are useful.  The most recent 
example is the following snippet

def testList = [0, 1, 2, 3]
def testRange = testList[0..2]

Which yields the error:

ERROR: Scripts not permitted to use staticMethod 
org.codehaus.groovy.runtime.DefaultGroovyMethods getAt java.util.List 
java.util.Collection

a straight index access works:  def testVal = testList[2]


For a critical plugin the script security sandbox has very poor usability. 
In addition to errors like the one above, the plugin does not allow fine 
grained permissions management. For example:


   - The only way to add new signatures is to repeatedly run a script until 
   a failure point.  This is painful when moving a script from a test 
   environment to a production environment.
   - You cannot individually manage approved signatures.  If a signature 
   needs to be removed, the only option is invalidating all approvals and 
   repeatedly run scripts to generate approvals.


Are there plans to improve the plugins usability?




-- 
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/f32384e8-d463-404b-bfd3-7b75cc976b9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to