-
Bug
-
Resolution: Fixed
-
Minor
-
-
script-security 1.43
What is the business impact?
The plugin cannot approve new java.util.Properties() - it asks you again and over again to approve the plugin.
What is the incorrect behaviour?
You are asked more than once to approve the same script.
What is the expected behaviour?
You should be asked only once to approve and then just work.
Step by step to reproduce
Create a pipeline job with the following code.
import java.util.Properties; Properties properties = new java.util.Properties(); node { echo 'Hello World' }
try to build the job
Go to manage jenkins -> script approval and approve
try to build again the pipeline and you will see that it still fails
Workaround
In my case, approving twice makes the work - but on a real environment, it seems the workaround might not work.
Regression
Not sure
If so, what versions did this previously work in?
Environment
Jenkins 2.32.3.2
script-security-plugin 1.33 and 1.31
- duplicates
-
JENKINS-50380 script-security doesn't handle a non-standard Collection without a constructor taking an array properly
-
- Resolved
-
- links to
The first approval is of new java.util.Properties (correct); the second, of new java.util.Properties java.util.Properties (incorrect, that is not the constructor being invoked).