Hi Carlos,
thanks for providing the logs.
If you check your log file Config-History-Defect.log.8 then you can see after line 2096, that some of the entries get deleted:
{{2016-07-08 04:11:41.865+0100 [id=96] FINE h.p.j.JobConfigHistoryPurger#doRun: checking for history files to purge (max age of 1 days allowed)
2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.FileHistoryDao#isCreatedEntry: historyDir: C:\Jenkins\config-history\com.cloudbees.jenkins.plugins.requestfilter.Rules\2016-07-06_15-48-59
2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.FileHistoryDao#isCreatedEntry: histDescr.getOperation(): Changed
2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.JobConfigHistoryPurger#purgeSystemOrJobHistory: Should delete: C:\Jenkins\config-history\com.cloudbees.jenkins.plugins.requestfilter.Rules\2016-07-06_15-48-59}}
So these history entries get deleted and should'n get shown anymore.
However, history entries with operation Created doesn't get deleted, even when they are older than the configuried max time. E.g.:
You create a job on July 15th. Then you do a couple of config changed of the job. When you have JobConfigHistory configured to delete all entries after 2 days and it's for instance July 20th, then all entries of this job get deleted. But the entry, which contains the Created operation, doesn't get deleted. It stays remain in the history.
You can test it with setting it to 1 day and leave it for 2 days. When you check your log, then you should see, that JobConfigHistory tries to deletes some entries (containing rows JobConfigHistoryPurger#doRun: checking for history files to purge (max age of 1 days allowed) and {{JobConfigHistoryPurger#purgeSystemOrJobHistory: Should delete: }})
Jochen
Hi Carlos,
could you provide a log of this (FINEST)?
I tried it and can't reproduce it (Jenkins 2.4, JobConfigHistory 2.14). The periodic checker runs once a day.
NOTE: The periodic check does NOT delete entries with operation "created".
Jochen