问题描述
我正在尝试使用 Mercurial 作为 VCS 为 TeamCity 设置构建触发器.现在触发器看起来像:
I am trying to setup a build trigger for TeamCity using Mercurial as the VCS. Right now the trigger looks like:
+:/**
提交变更集时触发此触发器.但是，我有 TeamCity 设置来标记 VCS 中的每个构建.标记过程会触发上述构建触发器，因此构建会陷入循环.
This trigger get fired when changesets are committed. However, I have TeamCity setup to tag each build in the VCS. The tagging process is firing the above build trigger so the build gets caught in a loop.
谁能建议一个 VCS 构建触发器来过滤掉标记过程?
Can anyone suggest a VCS build trigger that will filter out the tagging process?
推荐答案
添加触发模式:
-:/.hgtags
从构建触发器中过滤掉 .hgtags 文件.这是当源被 TeamCity 标记时被修改的文件.当此文件被排除时，标记操作将不会触发构建触发器.
filters out the .hgtags file from the build trigger. This is the file that gets modified when the source is tagged by TeamCity. When this file is excluded tagging operations will not fire the build trigger.
这篇关于如何为忽略标签操作的 TeamCity 设置 Mercurial VCS 构建触发器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！