如果你真的在对所有可用的测试进行持续集成，那么夜间构建将是多余的，因为当天检查的最后一个东西已经被测试过了.

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 来运行 all强>测试.这样可以让你及早发现很多 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.