Teamcity 在一次构建完成后不会收集更改
我们使用 Teamcity 进行构建集成。 目前我们正在与一个错误作斗争。 我们的 Teamcity 正在运行，代理也在运行。 当我们向 svn 提交某些内容时，teamcity 会收集所有更改，然后构建所有源。 此过程完成后，不再检查 svn。代理始终处于等待状态。
如何才能实现agent监听svn的变化呢？
We use Teamcity for our build integration.
Currently we're fighting with an error.
Our Teamcity is running and also an agent runs.
When we commit something into the svn, teamcity collects all changes and then builds all of our sources.
After this process is finished, the svn isn't checked anymore. The agent remains pending all the time.
How can we achieve that the agent will listen to svn changes?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您可以发布您为构建触发器设置配置的内容吗？我有一个 TeamCity 设置，其中 VCS 触发器配置为具有 60 秒的安静期。 （它会每 60 秒轮询 SVN 查找更改，如果发现任何更改，则触发构建）
奇怪的是，您的 TeamCity 配置会选择第一个构建，但不会选择任何后续构建。您是否也配置了正确的 VCS 根目录？
Can you post what you have configured for your build trigger settings? I've got a TeamCity setup with a VCS Trigger configured to have a quiet period of 60 seconds. (it'll poll SVN every 60 seconds looking for changes, and if any are found, trigger a build)
What seems strange is that your TeamCity configuration picks up the first build, but not any subsequent ones. Do you have the proper VCS root configured as well?
您使用什么版本的 TeamCity？在版本 5.x 中，TeamCity 仅在发现更改或更改收集时间过长时才在日志中报告更改。
此外，SVN 服务器和 TeamCity 之间可能存在计时问题（时间应该同步），特别是当您使用外部并且外部发生更改时。
另外，您可以尝试在 TeamCity 中启用调试日志记录（服务器配置 -> 诊断）。在这种情况下，teamcity-vcs.log 中应该有更多信息。
What version of TeamCity do you use? In versions 5.x, TeamCity reports changes in the log only when it found changes or when changes collecting took too long.
Also, there may be a timing issue between SVN server and TeamCity (time should be synchronized), especially if you use externals and changes occur in the externals.
Also, you may try enabling debug logging in TeamCity (server configuration -> Diagnostics). In this case, there should be more information in the teamcity-vcs.log.
查看安静期的文档，它指出这不是检查存储库的时间间隔。在这个时间范围内，您的 VCS 根不应发生任何事情才能启动。以确保它不会在一系列更改中的第一次签入时启动。
安静期是 TeamCity 在检测到最后一次 VCS 更改和将构建添加到队列之间的一段时间（以秒为单位）。也许您的 VCS 根范围太大，因此请检查-它经常出现吗？我在想也许你的所有项目都共享相同的 VCS 根，因此整个根是“安静”的情况很少见，这取决于许多其他正在致力于的项目？
现在看起来很模糊，但也许您已经明白了总体想法？
JetBrains 网站上的安静模式
Looking at the documentation on Quiet Period, it states that it's not the interval for checking the repo. It is the time frame during which nothing is supposed to happen to your VCS root for it to kick in. To ensure that it doesn't start on the first check-in in a series of changes.
Quiet period is a period (in seconds) that TeamCity maintains between the moment the last VCS change is detected and a build is added into the queue.Maybe your VCS root has a too big scope, so that check-ins occur to it very often? I'm thinking maybe all your projects share the same VCS root, so that it is rare that the whole root is "Quiet", depending on lots of other projects being committed to?
This looks vague now, but maybe you're catching the overall idea?
Quiet mode on JetBrains site