Continuous Integration Builds
Although daily builds were considered a best practice of software development in the 1990s, they have now been superseded. Continuous integration is now run on an almost continual basis, with a typical cycle time of around 20-30 minutes since the last change to the source code. Continuous integration servers such as CruiseControl or Hudson continually monitor the source code control system. When new changes are detected, a build tool such as Ant or Maven is used to re-build the software. Good practice today is also to use this as part of continuous testing, so that unit tests are re-run for each build, and more extensive functional testing (which takes longer to perform than the build) performed as frequently as its duration permits.
Read more about this topic: Daily Build
Famous quotes containing the words continuous, integration and/or builds:
“Perhaps when distant people on other planets pick up some wave-length of ours all they hear is a continuous scream.”
—Iris Murdoch (b. 1919)
“The more specific idea of evolution now reached is—a change from an indefinite, incoherent homogeneity to a definite, coherent heterogeneity, accompanying the dissipation of motion and integration of matter.”
—Herbert Spencer (1820–1903)
“The poet who speaks out of the deepest instincts of man will be heard. The poet who creates a myth beyond the power of man to realize is gagged at the peril of the group that binds him. He is the true revolutionary: he builds a new world.”
—Babette Deutsch (1895–1982)