It looks like it worked. I copied the scriptApproval.xml over to the production Jenkins and I found the approved methods listed there. Will know for sure if it works when I start my first production build.
I just added a few lines of new code and tried it out on my test Jenkins. I had to execute a build 8 times to each time add a new method to the approved list. This procedure to add to script approval one method at a time is ludicrous and time consuming. tirsdag 9. august 2016 10.45.11 UTC+2 skrev Björn Pedersen følgende: > > Hi, > > the approvals are stored in scriptApprovals.xml as hashes. I am not sure > if this file is transferrable, but from looking at the code ( > https://github.com/jenkinsci/script-security-plugin/blob/master/src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/ScriptApproval.java) > > it seems so. > > Björn > > Am Montag, 8. August 2016 12:36:13 UTC+2 schrieb Sverre Moe: >> >> I have had a test instance of Jenkins running while programming my >> workflow scripts. In this process I have had to go into In-process Script >> Approval time and time again to add method calls to the approved list. >> Now I have the need to load these into Jenkins production instance and I >> cannot run through the workflow scripts in the same way as I did in >> testing. There are aprox 15-20 approved methods. Having to run a test >> project 15-20 times to add methods to approved list is tedious. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/d80eed21-3fbc-4e3d-92f3-2a39ca3da908%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
