Teamcity 构建上的自动 VCS 标记 - 限制？
有人担心使用构建系统（TeamCity/CruiseControl）自动标记构建会创建太多标签，导致 Perforce 陷入困境。
我找到的唯一参考文献都说“除非你有数字，否则不要担心。”在污染 100+G 的存储库之前，我宁愿现在担心。
有没有人的系统每月进行 1000 多次构建，并且遇到过类似的情况？
There have been concerns that automatically tagging builds with build systems (TeamCity/CruiseControl) will create so many tags that Perforce will be bogged down.
The only references I've managed to find have said "unless you have numbers, don't worry about it." I'd rather worry now before polluting a 100+G repository.
Does anyone have systems doing 1000+ builds a month that have seen anything like this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可以考虑使用自动标签，它只包含一个视图（您正在识别的仓库部分）和一个修订号（通常是一个更改列表）。自动标签在数据库中放置的元数据非常少。
如果使用静态标签，则应定期归档旧标签以控制数据库的大小。
您可以在 Perforce 知识库中找到有关这些主题的更多信息。
You could consider using automatic labels, which simply contain a view (the parts of the depot you are identifying) and a revision number (usually a changelist). Automatic labels put very little metadata in the database.
If you use static labels, you should periodically archive old labels to keep the size of the database under control.
You can find more info on these subjects at the Perforce Knowledge Base.