Continuous integration is a development practice that requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by an automated build to detect problems early. Continuous integration differs from continuous delivery, which aims to deliver high quality software quickly, and continuous deployment, which automatically releases software passing automated tests into production. Continuous integration brings benefits like reducing integration issues and allowing faster software delivery by catching issues early.

1. Continuous
Integration
By: John Theory Roca

2. Agenda
What is Continuous Integration?
What is the difference between continuous integration vs. continuous delivery &
continuous deployment?
Why is continuous integration important?
Continuous Integration Process
Continuous Delivery Process
Continuous Deployment Process
Team Responsibility

3. What is continuous integration?
Is a development practice that requires developers to integrate code into a shared
repository several times a day.
Each check-in is then verified by an automated build, allowing teams to detect
problems early.
Is a strategy for how a developer can integrate code to the mainline continuously -
as opposed to frequently.

4. What is the difference between continuous
integration vs. continuous delivery &
continuous deployment?
Continuous Integration (CI) is the process of enforcing developers to merge their
code to mainstream branch or working code base as often as possible.
Continuous Delivery is the practice which aims to to deliver high quality software
really quickly every time.
Continuous Deployment refers to the release into production of software that
passes the automated tests.

5. Why is Continuous Integration important?
Continuous Integration brings multiple benefits to your organization:
Say goodbye to long and tense integrations
Increase visibility which enables greater communication
Catch issues fast and nip them in the bud
Spend less time debugging and more time adding features
Proceed in the confidence you’re building on a solid foundation
Stop waiting to find out if your code’s going to work
Reduce integration problems allowing you to deliver software more rapidly

6. Continuous Integration Process
Repository ( GitHub )
Master
Branch
Mainline
Branch
Integration Server MachineDev Machine
Integration server emails result
Checkout Code
Commits changes to mainline branch
Checkout
Code

7. Continuous Delivery Process
WORKING
APPLICATION
WORKING ON DEV
FEATURE
Dev Machine
APPLICATION CODE
VERSION CONTROL
BitBucket
GIT PULL
COMPOSER INSTALL
RUN TESTS
Jenkins
Production
git push
post hook
Manual deploy if tests passed

8. Continuous Deployment Process
WORKING
APPLICATION
WORKING ON DEV
FEATURE
Dev Machine
APPLICATION CODE
VERSION CONTROL
BitBucket
GIT PULL
COMPOSER INSTALL
RUN TESTS
Jenkins
Production
git push
post hook
automatic deploy if tests passed

9. Team Responsibility
Check in frequently
Don’t check in broken code
Don’t check in untested code
Don’t check in when the build is broken
Don’t go home after checking in until the system builds

10. The practices
Maintain a single source repository
Automate the build
Make your build self-testing
Every commit should build on an integration machine
Keep the build fast
Test in a clone of the production environment
Make it easy for anyone to get the latest executable
Everyone can see what’s happening

11. Web Links
Continuous Integration Integrate atleast Daily
Continuous Integration vs Continuous Delivery vs Continuous Deployment
Continuous Integration By Martin Fowler