Job Config History consumes a lot of space

Issue

  • Job config history plugin consumes a lot of space.
  • INodes are at 99% capacity.
  • Saving Jenkins system configuration is very slow.

Environment

  • CloudBees Jenkins Operations Center
  • Job Config History plugin
  • CloudBees Jenkins Enterprise

Resolution

The job config history plugin is a plugin designed to maintain the history of what has changed in the Jenkins job configuration and the system configuration. If a user has performed an operation to the job configuration and performed a save operation, then the history of what was changed (diff) and the user making the changes. Example:

By default the plugin is designed to maintain all history. The default settings can sometimes consume a lot of disk space or inodes which causes some performance issues. To resolve this we recommend setting up job configuration history plugin to not record as much data.

Recommended configuration

  • Use different history directory than default - Setting this option to a new location is good if you would like to store the job configuration history in another location other than $JENKINS_HOME/config-history (like another mount or another drive). We strongly encourage users to set this to another mount/drive as the job config history plugin will increase the number of inodes for the JENKINS_HOME directory.

  • Max number of history entries to keep - We recommend keeping this number to a minimum (about 1000). If left blank then all entries will be kept.

  • Max number of days to keep history entries - We recommend the max number of days to be 30 days.

  • System configuration exclude file pattern (default: queue\.xml|nodeMonitors\.xml|UpdateCenter\.xml|global-build-stats) - If there is configuration in the System configuration page which is not altered often or altering it does not impact users, then those options can be excluded from being added to the exclude file pattern. We recommend keeping the default pattern as the default pattern excludes the files which change the most frequently, and are not quite as important.

  • Do not save duplicate history - This option we recommend as this removes duplicate entries or entries where nothing changes.

  • Save Maven module configuration changes - We recommend disabling this option. When a maven project completes the job configuraiton is saved, which causes an increase in the amount of maven module configuration changes.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.