Cleanup tasks via the GUI

Comments

4 comments

  • Avatar
    Anush Ramani

    Hi Lee,


    Could you give us a bit more background on what you're trying to achieve? I can think of two things:



    1. You want to delete artifacts older than xx days to save disk space

    2. You don't want to retain artifacts that are part of a failed build to prevent inadvertent usage


    Do these cover it or did you have something else in mind?

    0
    Comment actions Permalink
  • Avatar
    LeeBenhart

    Hi Anush,


    Originally, I thought that was all I wanted to accomplish.  I have written a script which will perform these tasks.  While the folders are indeed gone, which is the primary objective, the history is still present.  I assume these are the database entries which I do not know how to access.  I think if this was something added to the admin management tasks, the historical entry could either be deleted as well, or modified to indicate the archive was intentianally deleted as not intented for production release.


    Lee

    0
    Comment actions Permalink
  • Avatar
    Anush Ramani

    Got it; you want a way to inidicate which build artifacts have been manually deleted.


    For reasons surrounding auditability, I don't think we'll support deleting a historical entry from the DB, however, being able to flag/tag manual deletions sounds interesting. Thanks for the feedback.


    We're spending a substantial amount of effort enhancing our server and agent administration capabilities in our upcoming releases and we'll definitely keep this feedback in mind.

    0
    Comment actions Permalink
  • Avatar
    LeeBenhart

    Artifact management is progressing nicely, great work.  I have been thinking about how I want to manage artifacts. Certainly managing based on disk space is nice if all artifacts are equal.  However I would like to have more rules in place, which means I still have to script something. Much of the time I know if a specific pipeline version is no longer of any use.


    It seems to me a nice addition to the PipelineActivity would be two flags (DELETE/KEEP).  Selecting DELETE for a pipeline would delete the physical artifacts related to that version and create a DB entry indicating physical files were deleted by <who> on <date>.  Of course, once deleted the keep option would not be available any longer. 


    In contrast, selecting KEEP would override the current artifact cleanup to NEVER delete the artifacts for this pipeline and create a DB entry indicating the action by <who> on <date>, primarily for record keeping. This of course could be modified if DELETE were selected later.


     


    Lee


     

    0
    Comment actions Permalink

Please sign in to leave a comment.