JobConfigHistory Plugin Best Practices Bee Bot July 13, 2022 10:22 Updated The content of this article has moved to the new documentation site. Related articles Auditing Best Practices How to Start, Stop or Restart your Instance? Why is my instance not getting the right information from CloudBees Update Center starting on October 19th, 2021? How to troubleshoot 'hudson.FilePath is missing' in a Pipeline run How to address the vulnerabilities in the CloudBees Security Advisory 2021-11-04 Comments 3 comments Sort by Date Votes Subhabrata Sarkar December 07, 2017 22:56 This was very useful for me, thanks 0 Judah Greenblatt September 16, 2019 13:09 Edited Proofreading: "Show build badges": the recommended setting is missing - from context I think this should be "Never". "Do not save duplicate history" is very confusing. Yes, it needs to be DISABLED to improve performance. However, this allows config-history to save duplicates, which increases disk space. Not much that can be done without changing the plugin itself, though. "Max number of history entries to keep": Reading the code shows that the number of entries is applied per config file (job, node, or global configuration file). 1000 seems excessive for history entries for a single file/node/job. I would think that 20-100 would be more reasonable. "Max number of days to keep history entries": There seems to be a bug in this plugin where this setting is applied to jobs at the top-level only - it is not applied to jobs inside folders. I'm trying to file a bug against the plugin to get this fixed. 4 Richard Dalton August 21, 2019 16:46 Great article, I didn't realise the importance of these settings! 0 Please sign in to leave a comment.