Continuous Integration.txt - You can develop a good...

You can develop a good software regardless of the technology you are working on,
by following certain fundamental practices:
Plan for code changes.
Perform the code changes, then compile and test.
Check the results.
Act on the results.
Adapt Continuous Integration to help you with seamless software development.
Continuous Integration (CI) is a software development practice, where developers
will commit (integrate) their code changes to a shared repository frequently.
When developers cultivate the habit of integrating their code changes regularly:
Changes will be typically small.
Errors can be detected quickly.
Pointing out the change that introduced an error can be done quickly.
Continuous Integration includes the following :
Source Code Control
Code Compile
Integrate Database Changes
Run Tests
Code Inspection
Source code control is the heart of Continuous Integration.
Source code must be managed using a version control system (VCS).
The different types are :
Local
Centralized
Distributed
Local Version Control System :
Code base maintained locally.
Centralized Version Control System (CVCS):
Code resides on a central base.
Developers :
create work branches.
do changes on the work branch.
publish changes to the central base
SVN is an example of CVCS.
Distributed Version Control System (DVCS):
Developers :
clone the central base in to their local machine.