Tag Info

New answers tagged

0

Continuous Integration is a process of continually integrating new changes with other peoples changes. The goal being to eliminate merge problems developing over time when many developers are changing the code independently in different directions. It is fashionable in commercial environments to have a centralised source control with an automated build ...


4

Automated testing would be a term for just running the tests every day, even if you only merged the code into a complete state once a month, or never. Arguably a bad idea, because if you keep different strands of development in different long running branches you will be merging the tests and code at the same time. And if the features interact in any way, ...


10

The gist of CI is to avoid any kind of long-term branches. If you have a team working on a product, a model opposed to CI is to pick a new requirement for a feature to develop for the product. Then the team creates a feature branch in the VCS, apart from the "trunk" or "master" branch, they develop and test the feature for several days in isolation, ...



Top 50 recent answers are included