[JIRA] (JENKINS-42537) script-appovals UX issues - administering them is hard
Title: Message Title James Nord updated an issue Jenkins / JENKINS-42537 script-appovals UX issues - administering them is hard Change By: James Nord It is not simple to manage script approvals. Say you have built up a lot of approvals over time and some newbie administrator approves one that is bad there is no way to remove individual entries.The only way to do this is to clear out the list and re-train the entire whitelist. But there is also no way to bulk submit (or even submit individual) entries for approval This means that removing one item will likely break all of you pipelines for hours or days until all of the approvals are re-added (until next time...) Acceptance Criteria * An administrator can add a new signature to the whitelist without having to create a Pipeline using the script signature. * An administrator can add a new signature to the blacklist without having to create a Pipeline using the script signature. * An administrator can remove individual signatures from the blacklist that where previously approved without removing every approval. An administrator can remove individual signatures from the whitelist that where previously approved without removing every approval. * An administrator can export the whitelist/blacklist and import it into a different jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42537) script-appovals UX issues - administering them is hard
Title: Message Title James Nord updated an issue Jenkins / JENKINS-42537 script-appovals UX issues - administering them is hard Change By: James Nord It is a complete pain not simple to manage script approvals. Say you have built up a lot over time and some newbie administrator approves one that is bad there is no way to remove individual entries.The only way to do this is to clear out the list and re-train the entire whitelist. But there is also no way to bulk submit (or even submit individual) entries for approval This means that removing one item will likely break all of you pipelines for hours or days until all of the approvals are re-added (until next time...) Acceptance Criteria * An administrator can add a new signature to the whitelist without having to create a Pipeline using the script signature. * An administrator can add a new signature to the blacklist without having to create a Pipeline using the script signature. * An administrator can remove individual signatures from the blacklist that where previously approved without removing every approval.An administrator can remove individual signatures from the whitelist that where previously approved without removing every approval. * An administrator can export the whitelist/blacklist and import it into a different jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42537) script-appovals UX issues - administering them is hard
Title: Message Title James Nord updated an issue Jenkins / JENKINS-42537 script-appovals UX issues - administering them is hard Change By: James Nord Summary: script-appovals UX issues - administering them is a complete PITA hard Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
