deconst/strider-deconst-content

Delete workspaces on successful build completion

Opened this issue · 0 comments

There isn't much value to keeping workspace state around after content's successfully been submitted to the content service API. Build workspaces also include two copies of all assets and so on which can fill the disk more rapidly than we'd like; see rackerlabs/nexus-control#504.

After a build completes successfully, just delete the workspace contents.