Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13246

disk usage peridocity should be configurable

    Details

    • Similar Issues:

      Description

      currently it runs every 60m. can be disruptive to team working environment. If run as part of build not so bad, but sweep of all jobs can be very bad.

      can we get a temporary cron knob to run it say only at 1am (or whenever) rather than the current every 60?
      can we have it skip builds/workspaces it has data for and populate the ones we know nothing about first?

        Attachments

          Activity

          Hide
          pixman20 pixman20 added a comment -

          It seems to me that the period configuration should be the same cron syntax used by the rest of Jenkins scheduling mechanisms (such as Build Scheduling). I agree this would be very helpful along with maybe a regular expression/configurable means for scanning builds/workspaces!

          Show
          pixman20 pixman20 added a comment - It seems to me that the period configuration should be the same cron syntax used by the rest of Jenkins scheduling mechanisms (such as Build Scheduling). I agree this would be very helpful along with maybe a regular expression/configurable means for scanning builds/workspaces!
          Hide
          scb147 Shawn Baker added a comment -

          Instead of a set time period, how about a trigger to initiate a disk usage check for a specific project. I could see a checkbox option in each project that, if checked, would trigger disk usage check after that project has completed successfully. Or maybe provided a post-build step to do so.

          Show
          scb147 Shawn Baker added a comment - Instead of a set time period, how about a trigger to initiate a disk usage check for a specific project. I could see a checkbox option in each project that, if checked, would trigger disk usage check after that project has completed successfully. Or maybe provided a post-build step to do so.
          Hide
          lvotypkova Lucie Votypkova added a comment - - edited

          I divided disk usage calculation into tree: calculation of builds, calculation of jobs (job directory without builds), calculation of job workspaces. Execution of these calculations is configurable as aforementioned (cron syntax used by Jenkins). Available since version 0.22, but I completely rewrited disk usage in version 0.22 and some bugs was reported and fixed in version 0.23, so I recommend version 0.23.

          Show
          lvotypkova Lucie Votypkova added a comment - - edited I divided disk usage calculation into tree: calculation of builds, calculation of jobs (job directory without builds), calculation of job workspaces. Execution of these calculations is configurable as aforementioned (cron syntax used by Jenkins). Available since version 0.22, but I completely rewrited disk usage in version 0.22 and some bugs was reported and fixed in version 0.23, so I recommend version 0.23.

            People

            • Assignee:
              lvotypkova Lucie Votypkova
              Reporter:
              moncreaff Greg Moncreaff
            • Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: