如何从 Teamcity 中触发构建中排除标签文件夹？
我最近安装了 Teamcity 5.0.3。我正在尝试为 .NET 2.0 VS2005 项目设置自动构建。我使用 NAnt 和 MSBuild 任务来执行构建。项目结构是典型的 SVN 结构
svn://localhost/ITools 是我的存储库，项目结构是
VisualTrack
trunk
branches
tags
我在 Teamcity 中创建了一个新项目，然后为该项目创建了构建配置。每次在 SVN VisualTrack VCS 中检测到更改时，我都会要求它启动构建。我还将其配置为在 VisualTrack/tags 中为每个成功的构建创建一个标签。我遇到的问题是，每次 teamcity 在标签下创建新标签时，都会触发构建。我只希望当某些开发人员将他或她的更改提交到主干时触发构建。我采取的下一步是创建一个构建触发规则，通过将触发模式指定为 -:VisualTrack/tags/** 来排除标签路径，但看起来它不起作用。我相信我指定的模式不正确。有人可以帮我解决这个问题吗？
谢谢，
贾亚。
I recently installed Teamcity 5.0.3. I am trying to setup automated build for a .NET 2.0 VS2005 project. I use NAnt and MSBuild task to perform the build. The project structure is a typical SVN structure
svn://localhost/ITools is my repository and the project structure is
VisualTrack
trunk
branches
tags
I created a new project in Teamcity and then created a build configuration for that project. I asked it to kick off a build everytime there is a change detected in SVN VisualTrack VCS. I also configured it to create a label in VisualTrack/tags for every successful build. The problem I am running into is that the build is getting trigerred everytime teamcity is creating a new label under tags. I only want the build to be triggered if some developer commits his or her changes into trunk. Next step I took was to create a build trigger rule to exclude the tags path by specifying a trigger pattern as -:VisualTrack/tags/**, but looks like its not working. I believe the pattern I specified is not correct. Can someone please help me resolve this issue?
Thanks,
Jaya.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以使用的另一种方法（适用于通常不使用主干的 VCS 系统（例如 Mercurial））是防止触发您提供给 TeamCity 的 VCS 用户名。
为此，请执行以下操作：
如果您使用此功能，您只需确保为 TeamCity 提供了使用您的 VCS 的自己的帐户。无论如何，这是一个很好的做法。
Another approach you can use, which works for VCS systems that don't typically use a trunk (such as mercurial), is to prevent triggering on the VCS username that you give to TeamCity.
To do this:
If you use this, you'll just want to make sure that you give TeamCity it's own account for using your VCS. That's good practice anyway.
我建议您将此项目的 TeamCity VCS 根 URL 更改为：
这是更典型的设置。您可以在 TeamCity 中轻松设置多个 VCS 根配置。这个 VCS 根只关心构建项目的主干区域，这听起来像是您想要的。
I'd suggest that you change your TeamCity VCS root URL for this project to be:
Which is a more typical setup. You can easily setup multiple VCS root configurations in TeamCity. This VCS root would only be concerned with building the trunk area of your project, which it sound like it what you want.