Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-18696

provide mechanism for user triggered job workspace cleanup

    Details

      Description

      At present, there is automated workspace cleanup based on a free space threshold.  This doesn't solve the case of forcing a mass cleanup when the workspace(s) for a job have corrupted state. Previously, an option to force a cleanup was provided on several jobs. However, this would only cleanup the workspace(s) in which the triggered build would be running and not all workspace(s) associated with that job.  A mechanism is clearly need to allow either all workspace(s) for all jobs to be cleaned up as the "nuclear option" or to allow all of the workspace(s) for a signal job to be purged.

        Attachments

          Activity

          Hide
          jhoblitt Joshua Hoblitt added a comment -

          Tim Jenness Gabriele Comoretto

          I have added a job parameter to the jenkins-node-cleanup job to "force" a clean up regardless of of the free disk space remaining.  This is intended only for exceptional circumstances such as when changing the miniconda installer version (until lsstsw is able to gracefully handle that scenario). I've started a new technote with instructions: https://sqr-030.lsst.io/#clean-up-all-job-workspaces

          Show
          jhoblitt Joshua Hoblitt added a comment - Tim Jenness Gabriele Comoretto I have added a job parameter to the jenkins-node-cleanup job to "force" a clean up regardless of of the free disk space remaining.  This is intended only for exceptional circumstances such as when changing the miniconda installer version (until lsstsw is able to gracefully handle that scenario). I've started a new technote with instructions: https://sqr-030.lsst.io/#clean-up-all-job-workspaces

            People

            • Assignee:
              jhoblitt Joshua Hoblitt
              Reporter:
              jhoblitt Joshua Hoblitt
              Watchers:
              Joshua Hoblitt, Tim Jenness
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: