Delete Artifacts when no longer required

Follow

Paul Clarkin

January 23, 2014 08:56

I have a couple of pipelines:

CI (Build / Deploy to CI) - this pipeline stores the built artifact in the artifact store, and has "Never delete artifcats" ticked.

QA (Fetch Artifcat from CI pipeline/Deploy to QA/Run tests etc)

Live (Fetch Artifact from CI pipeline/Deploy to Live)

The Go system also has many other pipelines from other teams and products. We have an issue where if you don't tick "Never delete artifacts" artifacts get deleted from the artifact store - even when the artifact store isn't full.  Maybe this in itself is an issue?

However, my suggestion is this; On a pipeline add the ability to delete old artifacts once a certain pipeline has complete. So in my above pipeline setup, if we are deploying version 5 to Live - once the pipeline completes, it would delete old artifacts (versions 4,3,2,1). Should we need the old versions we can obviously rebuild from source, but 99.9% of the time we don't need them.

The product involved has quite a large built artifact (200Mb +). Obviously after a number of builds, the artifact store gets quite full and has a knock on effect on other teams.

0

• 

  Sharanya Bathey January 23, 2014 10:22

  Hi Paul,

   

  You mentioned "We have an issue where if you don't tick "Never delete artifacts" artifacts get deleted from the artifact store - even when the artifact store isn't full." This might be because you have auto-delete artifacts on, you can find more details about this here - http://www.thoughtworks.com/products/docs/go/current/help/delete_artifacts.html

  As such, if the machine hosting Go has low artifacts disk space, Go will stop scheduling once the space goes below 100Mb. It will never delete artifacts automatically.

   

  Regards,

  Sharanya

   

  0

  Permalink
• 

  Paul Clarkin January 23, 2014 10:30

  We definitely want to delete any artifacts which are NOT marked as "Never Delete Artifacts". We've seen it deleting when the disk hasn't reached the limits set in the Admin.

  0

  Permalink
• 

  Sharanya Bathey January 23, 2014 11:19

  Hi Paul,

   

  In that case, we will investigate the issue from our end. Could you provide us with any information that might help us debug the issue better? Like your

  cruise-config.xml, the output of 'ls -lah' and the 'tree' command on the exact pipelines folder in the artifacts directory from which artifacts have been deleted and

  also the logs for Go around the time when the artifacts were deleted.

   

  Thanks,

  Sharanya

  0

  Permalink

Please sign in to leave a comment.