连续集成与夜间构建 [英] Continuous Integration vs. Nightly Builds

问题描述

阅读这帖子让我想知道;是一种比持续集成更好的情况下的夜间构建？答案的共识似乎是支持持续集成，是传福音还是真的没有理由使用每晚构建，当连续集成是一个选项时，是非常不利的。

Reading this post has left me wondering; are nightly builds ever better for a situation than continuous integration? The consensus of the answers seems to be pretty lopsided in favor of continuous integration, is that evangelism or is there really no reason to use nightly builds when continuous integration is an option?

推荐答案

如果你真的做所有可用测试的持续集成，每晚的构建将是多余的，因为在那一天检查的最后一件事已经测试。

If you're really doing continuous integration with all available tests, nightly builds would be redundant, since the last thing checked in that day would already have been tested.

另一方面，如果CI策略只涉及运行所有可用测试的子集，例如因为一些测试需要很长时间运行，那么您可以使用nightlies另外运行所有测试。这将让你早期捕捉许多bug，如果你不能及早赶上它们，你至少可以在一夜之间捕捉它们。

On the other hand, if your CI regime only involves running a subset of all available tests, for example because some of your tests take a long time to run, then you can use nightlies additionally to run all tests. This'll let you catch many bugs early, and if you can't catch them early, you can at least catch them overnight.

我不知道， ，如果这在技术上仍然是CI，因为你只是做一个部分构建每次，通过忽略一些测试。

I don't know, though, if that's technically still CI, since you're only doing a "partial" build each time, by ignoring some of the tests.

这篇关于连续集成与夜间构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！