TFS 滚动构建似乎在周末跳过构建 [英] TFS Rolling Build appears to skip building on the weekend

问题描述

在 TFS 2010 上，我们设置了一个构建脚本以自动运行并部署到我们的测试环境中，每 4 小时一次.因此，构建定义的触发器是滚动构建 - 累积签入直到前一个构建完成"，并选中构建频率不超过每 [240] 分钟"的复选框.我的解释是，如果构建发生在 16:25，并且在接下来的 30 分钟内有 3 次签入(最后一次发生在 16:52)，那么下一次构建将发生在 20:25.

On TFS 2010 we set up a build script to automatically run and deploy to our test environment no more than every 4 hours. So the trigger of the build definition is "Rolling builds - accumulate check-ins until the prior build finishes" with the check box checked for "Build no more often than every [240] minutes". The way I'm interpreting this is that if a build happens at 16:25, and there's 3 check-ins in the next 30 minutes (the last happening at 16:52), then the next build will happen at 20:25.

我们看到的问题是，如果这一系列事件发生在星期五，那么下一个触发构建要到星期一早上才会发生.我们在 TFS 的独立虚拟机上确实有两个构建代理，但所有机器都在 24/7 全天候运行.

The issue we're seeing is that if this sequence of events happens on a Friday, then the next triggered build doesn't occur until Monday morning. We do have two build agents on their own separate virtual machine from TFS, but all machines are up and running 24/7.

团队中的任何人都没有意识到会导致这种行为，所以我们不知道为什么会看到它.是我们对Rolling Build的意思理解有误，还是有什么配置设置忘记检查了?

There's nothing that anybody on the team is aware of that would cause this behavior, so we're at a loss for why we're seeing it. Are we simply misunderstanding the meaning of Rolling Build, or is there configuration setting we forgot to check?

就其价值而言，整个构建&部署过程需要 90-120 秒.所以在它还在建设中时没有发生任何签到.

For what it's worth, the entirety of the build & deployment process takes all of 90-120 seconds. So there were not any check-ins that occurred while it was still building.

推荐答案

Accumulate check-ins 的意思是当你签入一个变更集时，如果在 240 分钟内没有这个构建定义的构建，TFS 将把一个构建排入队列自动地.但如果不签入变更集，则不会有任何构建排队.

The Accumulate check-ins means that when you check-in a changeset, if there is no build of this build definition in 240 minutes, TFS will queue a build automatically. But if do not check-in a changeset, no builds will be queued.

应该在您编写时触发构建.第三次构建应该在 20:25 构建之后的第一次签到后触发，而不是在周六 0:25 之前.:)

Builds should be triggered as you wrote. 3rd build should be triggered after the first check-in after 20:25 build not before 0:25 on Saturday. :)

尝试检查变更集是否未检入隐藏在构建定义工作区中的位置(或检入未由构建定义工作区映射的位置).

Try to check if changesets were not checked into the location cloaked in the build definition workspace (or checked into the location not mapped by build definition workspace).

这篇关于TFS 滚动构建似乎在周末跳过构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！