from audit standpoint, we have to remove users from time to time.
it is a known issue/bug that it is not possible to remove users in cloudbees jenkins because if there is a git history, the user will not be deleted but recreated.
on a different note, removal should still go through and any entitlements across all jobs/folders should be removed but it doesn't work that way. The entitlements are not removed when doDelete api is done, inclusive of GUI.
We have to keep an inventory of all user entitlements of user and run submitRemoveMember api call for all such entitlements.
Why can't this be easy where we can glimpse all user entitlements like in other platform like GitHub enterprise.
Please sign in to leave a comment.