仅使用 CruiseControl.net 或 TeamCity 构建标记版本
目前，我们正在使用 CruiseControl.NET 作为许多 ASP.NET Web 项目的持续集成服务器，但我们也在评估 TeamCity。
这对于我们的构建服务器来说非常有用。
我们想要设置的是面向客户的测试服务器。我想，当我们很高兴我们的最新开发版本发布给客户端进行测试时，我们可以将其标记为SVN。
然后我想要第二个构建服务器来构建这个版本以供客户查看。
问题是这样的 - 有没有办法让 CruiseControl.NET 或 TeamCity 只构建存储库中最新标记版本的代码？
如果有人有任何替代建议，也将不胜感激！
We're currently using CruiseControl.NET as a continuous integration server for a number of ASP.NET web projects, but we're also evaluating TeamCity.
This is working great for our build server.
What we'd like to setup is a customer facing test server. I'm thinking that when we are happy for our latest development version to be released to the client for test, we could label it in SVN.
I'd then like a second build server to build this version ready for the client to see.
The question is this - is there any way to get either CruiseControl.NET or TeamCity to build only the latest labelled version of the code in a repository?
If anyone has any alternative suggestions, that'd also be greatly appreciated!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以在 Subversion 存储库中有一个指定的位置或分支，例如 \release，然后将第二个 TeamCity 构建服务器指向该位置。
当您对主干感到满意时，请覆盖现有位置。第二个构建服务器将拾取它，构建它，甚至将其部署到测试服务器。
You could have a designated location or branch in your subversion repository e.g. \release then point the second TeamCity build server at that.
When your are happy with trunk then overwrite the existing location. The second build server will pick this up, build it, and even deploy it to a test server.
我认为没有办法直接在 TeamCity 中执行此操作。但是，您可以配置构建触发器以过滤文件和/或用户。因此，如果您触摸给定文件来指示除了标签之外或而不是标签的发布状态，您可以使用它。
例如，触发过滤器可以是（未经测试）：
I don't think there's a way to do this directly in TeamCity. You can however configure your build trigger to filter on files and/or users. So, if you touch a given file to indicate release status in addition to or rather than labelling, you can use that.
The trigger filter could be, for example (untested):