Continuous integration (CI) is a software development practice that requires developers to integrate code into a shared repository multiple times per day, with each check-in triggering an automated build to detect problems early. CI benefits include avoiding integration issues at release time and spending less time on deployment activities. CI involves setting up a CI server with tools to automatically get the latest code, build, run tests, and notify results. Common tasks that can be automated through CI include building, running tests, reporting defects, notifying results, and deploying stable builds.

1. Continuous IInntteeggrraattiioonn ((CCII))
In Software Development
Prepared by Nhan Nguyen
Nov 2014

2. Have you ever faced:
Overnight to fix the integration defects when
rreelleeaassee ddaattee ccoommiinngg
No time left for testing and fixing defects found
Become tense, not confident when delivering
product to customer
2 / 09
Spent large time for deployment activities
(staging, production)

3. Because:
You don’t get benefits of
Continuous Integration
practice yet.
3 / 09

4. What is CI?
Continuous Integration (CI) is a development practice that
requires developers to integrate code into a shared repository
several times a day. Each check-in is then vveerriiffiieedd bbyy aann
automated build, allowing teams to detect problems early.
4 / 09

5. How to apply CI at Team-side ?
User story is defined and should be done no more than 3 working days
UT test script is developed along with functional code
Source code is integrated as soon aass uusseerr ssttoorryy ddoonnee
US #2
US #1
US #4
timeline
US #3
5 / 09
Repository

6. How to apply CI at Server side ?
Setting up CI server with CI tools
Making configurations for build, testing, deploying…
CI tool auto. gets latest code, make build/run tests… and notifies the
results
Repository
CI Server
6 / 09
timeline
US #1 US #2 US #3 US #4

7. Automated
Acceptance test
Overall Model
Development with
TDD, local build
`
Source Control
Server
Development with
TDD, local build
CI Server
Get the latest source code
Tag the stable build
Acceptance test
Server
Build Script
Feedbacks
7 / 09
Development with
TDD, local build
Production
Server
Automated Unit
test
Automated Unit test
(integrated code)
Automated build,
analyze code

8. What can be automated?
Make build
Report integration defects
Trigger to rruunn ddeeffiinneedd tteessttss
Report test coverage
Notify build/test results
Perform static code analysis
(coding standard, potential bug, low performance code…)
Deploy stable builds (staging, production)
With more than 1000 plug-ins, CI tools supported most of
platforms and programming languages, you can find more
8 / 09
benefits when applying CI practice.
Drawbacks:
Configuration is time consuming step but it just be done one time

9. References
CI tools: Jenkins, Bamboo, Cloudbees…
CI is one of 12 principles of Extreme Programming: link
Jenkins pplluugg--iinnss:: lliinnkk