TeamCity，某些配置没有清理.没有固定构建，没有依赖构建 [英] TeamCity, no clean-up for certain configuration. No pinned builds, no dependent builds

问题描述

我正在运行 TeamCity 5.我有一个特定的配置，它保留了过去一年左右的 3500 多个带有工件的过去构建.它占用了近 7 个演出空间，所以我需要清理旧版本.

I'm running TeamCity 5. I have one particular configuration that is preserving 3500+ past builds, with artifacts, from the last year or so. It's taking up almost 7 gigs of space so I need to clean up old builds.

该配置设置为清理早于 30 天或 5 个版本的所有内容.没有任何构建被固定.服务器上没有任何配置依赖于工件，即使有，我也没有设置防止依赖工件清理".其他构建配置会清理，但这个特定的配置不会.

The configuration is set to clean up everything older than 30 days or 5 builds. None of the builds are pinned. No configurations on the server depend on the artifacts, and even if they did I have un-set "Prevent dependency artifacts clean-up". Other build configurations clean up, but this particular one doesn't.

有人知道下一步要检查什么吗?

Anybody have ideas on what to check next?

推荐答案

我想通了.我不明白 TeamCity 如何保留旧版本.它保留了自第五个最古老的成功构建以来的所有构建，第五次成功构建是一年前.我将清理规则简化为清理比上次构建早 30 天以上且比第一个成功构建早的工件"，并删除了一些历史记录.现在，让开发人员修复他们的单元测试，以便更频繁地成功......;)

I figured it out. I wasn't understanding how TeamCity is preserving old builds. It's preserving all builds since the fifth oldest successful build, and the fifth successful build was a year ago. I reduced the cleanup rule to "Clean artifacts more than 30 days older than the last build and older than the 1st successful build", and got rid of some of the history. Now, to get the devs to fix their unit tests so this is successful more often... ;)

此外，您可以将-th 成功构建"字段留空并仅限制几天.

Also, you can leave the "-th successful build" field blank and limit just on days.

这篇关于TeamCity，某些配置没有清理.没有固定构建，没有依赖构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！