You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. In my case, there seems to be no way to "approve" a script.
I am logged in as a Jenkins admin, I edit the script and save it, which should result in automatic approval of the script, that is what he message is saying me.
The script edits get saved, but the script stays in the "not approved" state.
As a result it can not be run in a job, it is annoying because I use e.g. a short script to deactivate a job after each run. I use that script in a lot of jobs and all of those jobs end with an error state.
Hi. In my case, there seems to be no way to "approve" a script.
I am logged in as a Jenkins admin, I edit the script and save it, which should result in automatic approval of the script, that is what he message is saying me.
The script edits get saved, but the script stays in the "not approved" state.
As a result it can not be run in a job, it is annoying because I use e.g. a short script to deactivate a job after each run. I use that script in a lot of jobs and all of those jobs end with an error state.
Very annoying an unexpected behavior! Fortunately there is an equally annoying workaround.
Go to Script approval console. Somehow unapproved scriptlets code appears in the list and you can approve it there.
The same thing happens when you try to run an approved scriptlet after you edit it in the script UI.
Every small edit requires that you
run the edited scriptlet (fake run: since unapproved, it will not run)
approve it in Script Approval
run it with the edits
Very annoying an unexpected behavior! Fortunately there is an equally annoying workaround.
Go to Script approval console. Somehow unapproved scriptlets code appears in the list and you can approve it there.
The same thing happens when you try to run an approved scriptlet after you edit it in the script UI.
Every small edit requires that you
run the edited scriptlet (fake run: since unapproved, it will not run)
I'm uploading approvedScriptHashes in SHA-1 format to the server using jcasc . I can literally watch in the "jcasc view page" how when the scriptler page is activated, the latter takes all the hashes and converts them to sha-512. The problem is that after that, not a single script is actually approved. All scripts have green checkmarks, but inside the launch window there is a notification that the administrator must approve the script. How to get around or fix this?
I'm uploading approvedScriptHashes in SHA-1 format to the server using jcasc . I can literally watch in the "jcasc view page" how when the scriptler page is activated, the latter takes all the hashes and converts them to sha-512. The problem is that after that, not a single script is actually approved. All scripts have green checkmarks, but inside the launch window there is a notification that the administrator must approve the script. How to get around or fix this?
Activity
jenkins-infra-bot commentedon Sep 21, 2022
Raw content of original comment:
Very annoying an unexpected behavior! Fortunately there is an equally annoying workaround.
Go to Script approval console. Somehow unapproved scriptlets code appears in the list and you can approve it there.
The same thing happens when you try to run an approved scriptlet after you edit it in the script UI.
Every small edit requires that you
jenkins-infra-bot commentedon Jul 11, 2023
Raw content of original comment:
I'm uploading approvedScriptHashes in SHA-1 format to the server using jcasc . I can literally watch in the "jcasc view page" how when the scriptler page is activated, the latter takes all the hashes and converts them to sha-512. The problem is that after that, not a single script is actually approved. All scripts have green checkmarks, but inside the launch window there is a notification that the administrator must approve the script. How to get around or fix this?