Add a test cron job to see how it would clean up upload logs

The Puppet method for doing this seems to be what's causing its memory
usage to reach the size of the physical RAM in the system and take up to
4 days to complete a Puppet run. The test will show the files being
deleted and how long it takes, but won't actually delete them.

1 files changed, 8 insertions, 0 deletions

diff --git a/modules/buildsystem/manifests/scheduler.pp b/modules/buildsystem/manifests/scheduler.pp
index 47ac036e..9848f109 100644
--- a/modules/buildsystem/manifests/scheduler.pp
+++ b/modules/buildsystem/manifests/scheduler.pp
@@ -31,6 +31,14 @@ class buildsystem::scheduler {
                 age     => $buildsystem::var::scheduler::clean_uploads_logs_age,
                 rmdirs  => true,
             }
+
+            cron { 'clean uploads logs':
+                user    => $login,
+                # TEMPORARY to test what be deleted before replacing the above
+                command => sprintf("/usr/bin/find %s/uploads -xdev -type f -mtime +14 >/var/lib/schedbot/clean-uploads-logs-test.log", shellquote(${buildsystem::var::scheduler::homedir})),
+                hour  => '*/4',
+                minute => '51',
+            }
         }
         if ($buildsystem::var::scheduler::clean_uploads_packages_age != '0') {
             tidy { "${buildsystem::var::scheduler::homedir}/uploads/**/*.rpm":