JENKINS-73941 - ForceSandbox - Align Script-Security plugin with preexisting behavior in Workflow-CPS plugin #585
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JENKINS-73941 - Option to hide "Use Groovy Sandbox" for users without Administer permission globally in the system
Related to
In #584 we implemented the new forceSandbox logic in the Script Security Plugin instead of the Workflow-CPS Plugin.
The specific SandBox implementations are managed in the specific plugins, and in WorkflowCPS there are some functionalities not properly migrated in the previous PR to this repo
When the ForceSandbox option is enabled in the system:
We have aligned both behaviors.
In addition, for admin users, when running the FormValidation, we haven't changed the behavior (the ForceSandbox does not apply to admin), but we have added in the message some information about Sandbox not allowed in the system.
Testing done
New test cases were included to cover the described changes.
Submitter checklist