-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.49
Script Security Plugin 1.33
Due to limitations with the Script Security Plugin such as https://issues.jenkins-ci.org/browse/JENKINS-43722 I have implemented a custom backup and restore mechanism which overwrites the scriptApprovals.xml on disk. The option "Reload Configuration from Disk" does not reload the script approvals and a full restart of Jenkins is required before the approvals lists are re-populated. This seems counter to the description of the option which states: "Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk."
[JENKINS-47371] Reload Configuration from Disk does not work for Script Approvals XML
Description | Original: Due to limitations with the Script Security Plugin such as https://issues.jenkins-ci.org/browse/JENKINS-43722?filter=-3 I have implemented a custom backup and restore mechanism which overwrites the scriptApprovals.xml on disk. The option "Reload Configuration from Disk" does not reload the script approvals and a full restart of Jenkins is required before the approvals lists are re-populated. This seems counter to the description of the option which states: "Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk." | New: Due to limitations with the Script Security Plugin such as https://issues.jenkins-ci.org/browse/JENKINS-43722 I have implemented a custom backup and restore mechanism which overwrites the scriptApprovals.xml on disk. The option "Reload Configuration from Disk" does not reload the script approvals and a full restart of Jenkins is required before the approvals lists are re-populated. This seems counter to the description of the option which states: "Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk." |
Comment | [ I am experiencing this issue as well. I've automated updates of the \{\{$\{JENKINS_HOME}/nodejs.xml}} file, and was hoping that the changes would be made available in the UI following a reload from disk – unfortunately, this seems not to be the case. ] |
Labels | Original: configuration script-security | New: configuration script-security triaged-2018-11 |