问题描述
我想将我们的构建基础架构从CC.NET迁移到TeamCity。当然，TeamCity很漂亮的绿色。
I'm looking to migrate our build infrastructure from CC.NET to TeamCity. Admittedly pretty green with TeamCity at this point.
一个潜在的显示是，我们需要我们的构建配置与它构建的源代码一起进行版本控制。 CC.NET使得这很容易，是一个非常有用/强大的功能。
One potential show-stopper is that we need our build configuration to be version-controlled alongside the source code it builds. CC.NET makes this pretty easy and is a very useful/powerful feature.
从我的调查，你可以改变TeamCity存储其配置/数据，但没有官方文档（这里也没有其他主题）似乎引用它放在一个版本控制的位置，如TFS，Perforce或ClearCase。
From my investigation you can change where TeamCity stores its config/data, but none of the official documentation (nor other topics here on SO) seem to reference placing it in a version-controlled location such as TFS, Perforce or ClearCase.
这可能是因为TeamCity假设R / W访问任何配置文件和底层VCS使文件R / O需要签入/签出语义，这将混淆TeamCity并停止它的工作。
Could it be that if TeamCity assumes R/W access to any config files and the underlying VCS makes files R/O requiring check-in/check-out semantics that this'll confuse TeamCity and stop it working.
有人在这里有版本控制的经验TeamCost中的TeamCity构建配置？
Does anyone here have experience of version controlling TeamCity build configuration in Team Foundation Server (or similar)?
感谢，
Jack
Thanks,Jack
em> FYI - 似乎是SO上唯一类似的线程。
...和相关的官方文档谈论迁移配置和/或备份它，这是接近但不是真的相同的事情。
FYI - How does one version control the configuration of a TeamCity project? seems to be the only similar thread here on SO.http://confluence.jetbrains.net/display/TCD7/How+To... and related official docs talk about migrating config and/or backing it up, which is close but not really the same thing.
推荐答案
这已在TeamCity 9中引入：
This has been introduced in TeamCity 9:
这篇关于TeamCity的版本控制（例如在TFS中）构建配置 - 是可能吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！