Quiet Period in Continuous Integration:
A Continuous Integration build should be run often, ideally every commit would result in a Continuous Integration build. But that’s often not possible or realistic or even desirable in the real world. For example, lets say that to fix an issue the developer had to modify two source files. He first commits one of the files forgetting for the moment about the other one. A few seconds later he realizes that the other file needs to be committed as well. This will result in two commits. Ideally, there should be a Continuous Integration build that captures both these commits. If there were a build between the two commits then such a build would fail.
To ensure that such a situation will result in a single Continuous Integration build, we can use a Quiet Period. The Quiet Period is a length of time that the source code repository must be without any commits before a Continuous Integration build can proceed. Ideally, this length of time will be long enough for the developer to make all commits that are part of the same change to the source code and short enough to still get quick feedback on commits. Chalrie sets his at one minute. The purpose of the Quiet Period is to make sure that the source code taken for a Continuous Integration build contains a consistent set of changes. AnthillPro fully supports a configurable Quiet Period duration.
Post a Comment