0

Currently my team is using local build agents for our on-premise TFS 2015 installation. We've installed these build agents on our own development machines. However we are having issues limiting the space required for the continuous integration builds.

Our disk space is limited. Consequently we have to remove old build tasks (including sources and artifacts) manually to clean-up disk space.

Is there some way to automate this? Preferly by telling TFS to automatically remove older build tasks.

Herman Cordes
  • 4,628
  • 9
  • 51
  • 87

1 Answers1

1
  1. You can specify build retention policies, which will automatically delete old completed builds to minimize clutter. You modify these policies on the Retention tab of your build definition. Retention policies will delete the items below:

    • The build record
    • Logs
    • Published artifacts
    • Automated test results
    • Published artifacts
    • Published symbols
  2. Currentlt, server drops are deleted when a build is deleted but drops to UNC shares are not. This has been fixed on Team Services and is in Team Foundation Server '15', which is currently in prerelease. Check: https://connect.microsoft.com/VisualStudio/feedback/details/1513256/build-preview-drop-folder-not-deleted-when-build-is-deleted

  3. Working folder on your machine won't be deleted . In order to delete UNC drops and working folder, you can add a task Delete files in your build definition to delete working folder and drop folder.

Cece Dong - MSFT
  • 29,631
  • 1
  • 24
  • 39