[JENKINS-35391] Improve UX of Groovy sandbox for Pipeline builds

Nobody has claimed this yet.

There are several kinds of issues with the user experience of the Groovy sandbox as applied to Pipeline especially:

• Lots of legitimate method calls are not whitelisted by default. We need to greatly expand the bundled whitelist.


• Some calls are not properly classified for script approval. Typically I fix these as they are reported, though there are some open.


• User experience of handling script security generally is sub-par.

---
Originally reported by jglick, imported from: Improve UX of Groovy sandbox for Pipeline builds

• assignee: jglick
  
• status: Open
  
• priority: Major
  
• component(s): script-security-plugin, workflow-cps-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 7
  
• imported: 2025-12-07
  

There are several kinds of issues with the user experience of the Groovy sandbox as applied to Pipeline especially:




	
Lots of legitimate method calls are not whitelisted by default. We need to greatly expand the bundled whitelist.

	
Some calls are not properly classified for script approval. Typically I fix these as they are reported, though there are some open.

	
User experience of handling script security generally is sub-par.

Start by reviewing the script-security-plugin and workflow-cps-plugin components named in the issue, then trace how Groovy sandbox whitelist and script approval handling are organized. The issue describes several broad UX goals but names no files, tests, entry point, or concrete completion criteria, so the scope must be clarified before work begins.

Written by the indexing model from the issue text.