Fix preapprove() leaving scripts in pendingScripts after approval #908
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The
preapprove()method adds script hashes toapprovedScriptHashesbut does not remove matching entries frompendingScripts. This causes scripts to appear with apply/deny buttons in the Jenkins UI even though their hashes are already present inscriptApproval.xml'sapprovedScriptHashes.The scripts are technically approved (hash exists in
approvedScriptHashes) but the UI incorrectly shows them as pending because they remain in thependingScriptslist.Solution
This fix makes
preapprove()consistent withpreapproveAll()by callingremovePendingScript()to remove the pending entry after adding toapprovedScriptHashes.Changes
preapprove()method to store the hash in a variableremovePendingScript(hash)after adding toapprovedScriptHashesThis makes the behavior consistent with
preapproveAll()which already clearspendingScriptsafter approval.Submitter checklist