Manuel Cardenas
added a comment - 2017-08-16 09:17 Sorry for the delay, Jesse Glick . No, I have not make the test without using the envinject plugin, will try to perform the test and update the case cc/ Oleg Nenashev

Sort of as designed, though UX could be improved. Approved scripts and pending approvals are distinct things. Once a script is approved, only the fingerprint is retained, not the full text nor the approval context. So when you clear approved scripts, it would be impossible to return them to a pending state. After jobs are loaded on next Jenkins restart, there is no trace of the previous approval, so it is readded to the queue.

Jesse Glick
added a comment - 2017-08-16 12:37 Sort of as designed, though UX could be improved. Approved scripts and pending approvals are distinct things. Once a script is approved, only the fingerprint is retained, not the full text nor the approval context. So when you clear approved scripts, it would be impossible to return them to a pending state. After jobs are loaded on next Jenkins restart, there is no trace of the previous approval, so it is readded to the queue.

I am seeing the same problem. An administrator accidentally cleared our script approvals and we cannot add them back.

Things brings up a big issue with the UX. There is no "Save" option on the script approvals page, so as soon as the Clear Approvals is selected there is no going back. It would be safer if there was a separate Save button for activating the change. In addition, there is no way to restore previous script approvals using a "Configuration Change History", similar to what one can do with jobs. I haven't been able to find an issue tracking these, so I may open new ones.

Joe Harte
added a comment - 2017-08-18 11:05 - edited I am seeing the same problem. An administrator accidentally cleared our script approvals and we cannot add them back.
Things brings up a big issue with the UX. There is no "Save" option on the script approvals page, so as soon as the Clear Approvals is selected there is no going back. It would be safer if there was a separate Save button for activating the change. In addition, there is no way to restore previous script approvals using a "Configuration Change History", similar to what one can do with jobs. I haven't been able to find an issue tracking these, so I may open new ones.