TeamCity 不触发自动构建
我对持续集成很愚蠢，并注意到一种似乎不正确的行为。
我正在将 Mercurial 与 TeamCity 一起使用。当我推送更改时，TeamCity 会检测到更改，但不会自动运行构建。这是正确的行为吗？他不应该检测到更改并自动运行构建吗？
I'm dumb with continuous integration and noticed a behavior that does not seem right..
I'm using Mercurial with TeamCity. When I push changes the TeamCity detect the changes but don't run the build automatically. This is correct behavior? He should not detect the changes and run the build automatically?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
默认情况下，TeamCity 中不会将触发器添加到构建配置中。您需要转到配置设置，然后单击“构建触发器”，然后单击“添加触发器”。我相信您正在寻找的触发器类型是“VCS 触发器”。
此功能的文档可以在此处找到。
Triggers are not added to build configurations by default in TeamCity. You'll need to go to the settings for the configuration and click on "Build Triggers" then "Add Trigger". The type of trigger I believe you are looking for is a "VCS Trigger".
The documentation for this feature can be found here.
我相信我的问题是误解了分支过滤器的需求。我以为我应该输入 GIT 参考 我想要从这触发构建
这对我来说不起作用
这就是最终发现的（我认为）是它要求 TeamCity 本身内部的分支名称（帮助文本显示“以 +|- 形式的换行符分隔的规则集：逻辑分支名称”）
这对我有用，可以从分支触发构建（GIT ref refs/heads/master 对我来说，回顾一下你的 VCS根设置）以及除标记为“releases/6.7.3”、“releases/6.8.30”、“releases/6.8.32”和“releases/6.8.34”的分支之外的所有其他分支
I believe my issues was misunderstanding what was needed in Branch Filters. I thought I was supposed to enter the GIT refs I wanted to have builds triggered from
This wasn't working for me
And this is what finally figured out (I think) is that it is asking for the branch names inside TeamCity itself (the help text says "Newline-delimited set of rules in the form of +|-:logical branch name")
This worked for me, to trigger builds from the branch (GIT ref refs/heads/master for me, look back in your VCS Root setup) and all other branches except those labeled "releases/6.7.3", "releases/6.8.30", "releases/6.8.32" and "releases/6.8.34"