Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Some of the configurations in the history of our jobs contain sensitive information like passwords.
For such cases, it would be of big advantage if Jenkins user could delete such configurations from the job's history.
Attachments
Activity
Andreas Galek
added a comment - Unfortunately, the buttons 'Delete Entry' don't appear in a build job as long as you don't have full global administrative privileges in Jenkins!
'Delete Entry' should be visible for every user having 'Configure Build Job' privileges in a build job.
Andreas Galek
added a comment - Unfortunately, the buttons 'Delete Entry' don't appear in a build job as long as you don't have full global administrative privileges in Jenkins!
'Delete Entry' should be visible for every user having 'Configure Build Job' privileges in a build job.
Hank Zill
added a comment - I just wanted to chime in and say that allowing people with build job privileges to delete change entries makes this plugin much less useful from an auditing and compliance perspective.
Hank Zill
added a comment - I just wanted to chime in and say that allowing people with build job privileges to delete change entries makes this plugin much less useful from an auditing and compliance perspective. We implemented the possibility to manage the delete entry rights via matrix-based security.
Default is admin, still. It's going to be released soon.
Done and released with version 1.5 on 09.09.2019.