 |
ContinuesIntegrationContinuous IntegrationRef from http://en.wikipedia.org/wiki/Continuous_Integration : Continuous Integration is the practice of integrating early and often, so as to avoid the pitfalls of "integration hell". The ultimate goal is to reduce timely rework and thus reduce cost and time. When done well, continuous integration has been shown to achieve these goals. Continuous integration itself refers to the practice of frequently integrating one's code with the code that is to be released (often this is the trunk, but that is not necessarily the case). The term 'frequently' is open to interpretation, but is often taken to mean "many times every day". Multi-Stage Continuous IntegrationRef from http://en.wikipedia.org/wiki/Multi-stage_continuous_integration : Multi-Stage Continuous integration allows for a high degree of integration to occur in parallel while vastly reducing the scope of integration problems. Multi-Stage CI takes advantage of a basic unifying pattern of software development: software moves in stages from a state of immaturity to a state of maturity, and the work is broken down into logical units performed by interdependent teams that integrate the different parts together over time. What changes from shop to shop is the number of stages, the number and size of teams, and the structure of the team interdependencies. The Most Frequent Refered Resources about Continues Integration
Contact: Goose |