Disable Teamcity agent auto deleting workspaces when machine out of space

Hello Chris,

As per this article, you could disable clean-up of workspaces (TeamCity will remove workspaces related to the checkout directories which were not used for 8 days by default) by using this build parameter (either defined in buildAgent.properties or as a Root project parameter):

teamcity.perforce.workspace.cleanup=false

Please let me know if this approach works for you.

Unfortunately this does not help, sorry i should have said that this was already set. I have these settings inside the buildagent.properties:

teamcity.agent.filecache.publishing.disabled=true
teamcity.agent.failBuildOnCleanCheckout=true
teamcity.perforce.workspace.cleanup=false
system.teamcity.agent.build.checkoutDir.expireHours=never
teamcity.artifacts.useZip64=true

But checkout dir are still been cleaned up when space is low

Cheers,
Chris

Hello Chris,

Could I ask you to share the <build agent install folder>/logs/teamcity-agent.log and teamcity-vcs.log files for any agent where the workspaces were removed recently? You could use https://uploads.jetbrains.com to do so in a private manner. In addition, if you could enable generic debug for any agent (to try and catch extra logging on the moment when workspace is gone), it would be helpful.

is teamcity.perforce.workspace.cleanup only for perforce？

Hello!

Yes, this property is Perforce-specific. Could you please let me know what VCS you are using and what behavior you would like to ensure? 

we use git ,and have the same problem with Chris,

here are some log

[2021-01-26 15:36:43,019]   INFO - l.directories.DirectoryMapImpl - Cleaning up old checkout directories. Default lifetime = 192 hour(s)
[2021-01-26 15:36:43,054]   INFO - ctoryMapDirectoriesCleanerImpl - Deleting /Volumes/NVME/opt/TeamCity/buildAgent/work/42e651f2319b82d0. Build directory has expired, unused or free disk space is needed
[2021-01-26 15:36:43,067]   INFO - rectories.DirectoryCleanerImpl - Move directory /Volumes/NVME/opt/TeamCity/buildAgent/work/42e651f2319b82d0 to /Volumes/NVME/opt/TeamCity/buildAgent/work/.old/42e651f2319b82d0_8 for cleaning
[2021-01-26 15:36:43,067]   INFO -    jetbrains.buildServer.AGENT - removeDirectoryRevisionInfo: currentConfigurationFile exists: true
[2021-01-26 15:36:43,068]   INFO -    jetbrains.buildServer.AGENT - Deleted configuration file 42e651f2319b82d0.xml, because checkoutDirectory /Volumes/NVME/opt/TeamCity/buildAgent/work/42e651f2319b82d0 is removed
[2021-01-26 15:36:43,069]   INFO - dDirectoryBasedCleanupRegistry - Start deleting files from /Volumes/NVME/opt/TeamCity/buildAgent/work/.old
[2021-01-26 15:37:07,949]   INFO - dDirectoryBasedCleanupRegistry - Stop deleting files from /Volumes/NVME/opt/TeamCity/buildAgent/work/.old. 0 file(s) were deleted. 
[2021-01-26 15:37:07,949]   INFO - dDirectoryBasedCleanupRegistry - Removing files from /Volumes/NVME/opt/TeamCity/buildAgent/temp/.old
[2021-01-26 15:41:42,924]   INFO - r.artifacts.impl.HttpDiskCache - Cleaning up items with life time in cache greater than 172800 seconds
[2021-01-26 15:41:42,924]   INFO - r.artifacts.impl.HttpDiskCache - Finished cleaning up expired items, 0 items removed

Hello!

If you need to ensure specific checkout directory is never removed during the build, you could use the following build configuration property (as described in this article):

system.teamcity.build.checkoutDir.expireHours=never

If you have this property set for a build configuration (or a project), this will ensure that the checkout directories they use will always persist. The property can also be set to a numeric value to define how old the directory has to be in order to be removed on expiration/cleanup routine.