- Best Practice for auditing Jenkins instance usage: “WHO did WHAT?”
- CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
- CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
- CloudBees CI (CloudBees Core) on traditional platforms - Client controller
- CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
- CloudBees Jenkins Enterprise
- CloudBees Jenkins Enterprise - Managed controller
- CloudBees Jenkins Enterprise - Operations Center
- CloudBees Jenkins Platform - Client controller
- CloudBees Jenkins Platform - Operations Center
- CloudBees Jenkins Distribution
- Jenkins LTS
There are two open-source plugins that allow you to perform audits in Jenkins:
- Audit Trail Plugin: Adds an “Audit Trail” section in your Jenkins main configuration page, where it is possible to define where to save logs on who performed particular operations on Jenkins. To get additional information about this plugin, please refer to How does Audit Trail plugin work?.
- Job Config History Plugin: stores all the changes made to jobs (history), saving the
config.xmlof each job. For each change, it is possible to see the record of the change, compare the difference between the new and the old version and restore a previous version. It is also possible to keep track of the changes made to the system configuration.
- IMPORTANT: This plugin can become a performance killer if you do not follow the recommendations provided in JobConfigHistory Plugin Best Practicest.
Complementary to the Open Source plugins, CloudBees offers:
- User Activity Monitoring: provides you with a summary of user activity, CSV exports of user access details, and JSON reports that can be exported to other applications. The User Activity Monitoring plugin helps you understand licensing and entitlement.