As of Jenkins Security Advisory 2017-10-11 CommandLauncher configuration enforces RUN_SCRIPTS, which is awkward for cases where a lower-privileged user is permitted to configure other aspects of an agent. The launcher should be moved out of core into a plugin that can depend on script-security for a regular approval workflow.
Originally reported by 
jglick, imported from: Split CommandLauncher into a plugin and integrate with script-security
- assignee: jglick
- status: Resolved
- priority: Major
- component(s): core
- label(s): security, split-plugins-from-core, ux
- resolution: Fixed
- resolved: 2017-10-17T20:57:14+00:00
- votes: 0
- watchers: 3
- imported: 2025-11-24
Raw content of original issue
As of Jenkins Security Advisory 2017-10-11 CommandLauncher configuration enforces RUN_SCRIPTS, which is awkward for cases where a lower-privileged user is permitted to configure other aspects of an agent. The launcher should be moved out of core into a plugin that can depend on script-security for a regular approval workflow.
As of Jenkins Security Advisory 2017-10-11 CommandLauncher configuration enforces RUN_SCRIPTS, which is awkward for cases where a lower-privileged user is permitted to configure other aspects of an agent. The launcher should be moved out of core into a plugin that can depend on script-security for a regular approval workflow.
Originally reported by
jglick, imported from: Split CommandLauncher into a plugin and integrate with script-security
Raw content of original issue