[JIRA] (JENKINS-61199) Job Configuration History Plugin doesn't seem to honor "Max number of days to keep history entries" for deleted jobs

[Martin.Jost@nokia.com (JIRA)]

Martin Jost created an issue

Jenkins / JENKINS-61199 Job Configuration History Plugin doesn't seem to honor "Max number of days to keep history entries" for deleted jobs Issue Type: Bug Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2020-02-24 14:18 Environment: Jenkins 2.204.2 (newest LTS) Job Configuration History Plugin 2.24 (most recent) Java OpenJDK8U-jdk_x64_linux_hotspot_8u232b09 Running on Redhat 7 No container Labels: plugin Priority: Minor Reporter: Martin Jost I have configured the plugin as follow: Use different history directory than default:: [Empty] Max number of history entries to keep: 20 Max number of days to keep history entries: 365 Max number of history entries to show per page: [Empty] Configuration exclude file pattern: queue|nodeMonitors|UpdateCenter|global-build-stats Do not save duplicate history: ON * Save Maven module configuration changes: ON * Show build badges: Always Exclude users: [Empty] Now to my amazement, I found on the FS files like: drwxr-xr-x 6 lthy ne 4096 Nov 11 2016 home/config-history/jobs/testJob_deleted_20161111_152741_018 drwxr-xr-x 6 lthy ne 4096 Jun 29 2016 home/config-history/jobs/testMultiBranch_deleted_20160629_190653_773 drwxr-xr-x 8 ltphy ne 4096 Aug 30 2016 home/config-history/jobs/Try1_deleted_20160830_093601_349 So this looks like the job got deleted in 2016. (I have similar cases for later years.) With "Max number of days to keep history entries: 365" I would have expected everything deleted more than a year ago to be removed. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[mail@jochen-fuerbacher.de (JIRA)]

Jochen A. Fürbacher commented on JENKINS-61199

Re: Job Configuration History Plugin doesn't seem to honor "Max number of days to keep history entries" for deleted jobs This might be a permission issue. Your ls shows two different users: lthy and ltphy. The files only have write permission for their own user, so the user lthy cannot delete a file of user ltphy and vice versa. What's your jenkins system user? If your jenkins system user isn't lthy nor ltphy, JobConfigHistory cannot delete these files. Could you also check the jenkins logfile? You should see some entries like Should delete: <filename> and maybe a warning like problem deleting history file: <filename>.

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)