Continuous İntegration

They say a picture tells much more..from that truth i draw the big picture makes things clear

Continuous integration is a practise comes from Extreme Programming. In large projects  all developers makes their indiviual works but when it is time to integrate them it is a big problem. A lot more time has to be spend to solve integration problems. So each member of a team should make their commits frequently to a repository  this gives the team to re-use the common code early and recognise integration problems early.  An integration server such as hudson, jenkins etc. builds code, runs unit & integration test, inspects the quality of the code, deploys the build, updates the database to the same version of the code and runs Automated User Interface tests.Then developers look at the test results. QA manager  looks at Continuous Inpestion results. He/she opens issues on issue tracking system which continuous inspection rules marked as major or critical. Then the errors found in tests results are fixed and improvements are made for QA.  Finally a clean integrated work is ready for the production. You may read alot more about CI on Matin Fowler’ site.