Continuous Integration (Part 1
)
What is Continuous Integration ?
Continuous Integration is software development practice
where members of a team integrate their work frequently, usually each person integrate
at least daily – leading to multiple integration per day. Each verification is verified
by an automated build (including test) to detect integration errors as quickly
as possible.
How exactly it’s different from normal build?
In our normal build.
- 1) Developer changes the code to develop new feature or may be it fix the open bug.
- 2) They do unit testing (or not do J )
- 3) They commit their code.
- 4) Everyone who pull the code
- 5) And if code has error every one get hit of the bad or buggy code.
May be even if developer do the unit testing there is possibility
that that code failed in integration testing.
Also there is a chance of manual error while deploying code
on client side.
Solution of this problem is Continuous Integration !!!! (More in Part II)
I explain current deployment and problem with below images
1) Normal Team where two different component build by two different team members.
2) When One team member test hi code and commit.
3) When second team member get code and it break his/her whole system :-(
So please refer my Continuous Integration (Part II )
