The document outlines the principles and practices of Continuous Integration (CI) in software development, emphasizing the need for frequent code check-ins and automation to enhance efficiency and reduce errors. It discusses the importance of maintaining a shippable mainline and provides a framework for implementing CI, including guidelines for developers to follow. Additionally, it touches on related concepts such as Continuous Delivery and Continuous Deployment, highlighting their significance in the software lifecycle.

1. ContinuousIntegration 101
by Manuel Spezzani
Bologna, October30, 2014

2. Manuel Spezzani
Technical Lead
IConsulting S.p.A.
m.spezzani@iconsulting.biz
manuel@indyco.com
@manuelspezzani
http://it.linkedin.com/in/manuelspezzani/it

3. Me, myself& indyco

4. WhatisContinuousIntegration

5. Continousintegrationbefore

6. Continousintegrationafter

7. A basiccontinuousintegrationprocess
At everycommit:
Getlatestsources
Build
Test
Package
Evenifoneminortest fails, the buildismarkedasRED

8. A basiccontinuousintegrationprocess
No IDE allowed!
Sourcescomesfrom ONE repository
Buildscripts are sources
Database scripts are sources
Test everything!
Database scripts countsaseverything
No-oneneeds100% coverage, everyoneneeds100% confidence!

9. Continousintegrationand me
More discipline
Checkinfrequently
Don’tcheckinbroken/ untestedcode!
Don’tcheckinwhenthe buildisbroken
Don’t go home after checking in until the system builds
http://www.thoughtworks.com/continuous-integration

10. Why?

11. Efficiency
AutomateEverything
No monkey-work
Coded, self-documentedprocesses

12. Reproducibility
Reduce human errors
Artifactversioningand traceability

13. Release early–release often
Ensurethe mainlineisalwaysshippable
Reduce packaging and release time

14. Multiple configurations
Environment
OS
Browsers
Network
…
Third-party integrations
Databases
Libraries
…

15. Whereto start?

16. Set a goal: 1-click release
Clear and easy to measure
It’seasy to estimate a «ROI»
Youcan sell itto yourboss!
Involvesa lotof processes
Probablyitwillchangethe way youwork

17. Set rules, and followthem
Developers haveno accessto C.I. servers
No log-in access
No file-systemaccess
No-oneisallowedto release manually

18. Build== Code
Codingprinciplesapplies
KISS
DRY
YAGNI
…
The buildshouldevolve with yourproject

19. Wichone?

20. Anti-Patterns

21. Fragility
Occasionalfailures
«Don’tstop thatbuild» syndrome

22. Interference
Sharedresources
Limitationon concurrentbuild
Limitationon concurrenttests

23. Reproducibility
Dependencyhell
Developers haveto accessthe CI machinesto throubleshootbuildissues
The buildscript can’tbe executeda standard devmachine

24. Poorfeedback
The buildtakestoolong
Email notifications

25. Movingforward

26. Personal build

27. Nightlybuildasa companion
Usefulwhen:
Workingon large projects, with lotof integration/ UI tests
Resource intensive builds
Be careful:
Dailyintegrationisnotenough!
http://www.alittlemadness.com/2009/01/27/continuous-integration-myth-ci-vs-nightly-builds/

28. Continuousdelivery
Your software is deployablethroughout its lifecycle
You can perform push-button deployments of any version of the software to any environment on demand
http://martinfowler.com/bliki/ContinuousDelivery.html
http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-continuous-deployment

29. Continuousdeployment
Your software is deployedthroughout its lifecycle
Is it a good idea or not? It depends on your business!
http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-continuous-deployment

30. …and more!
Automatedperformance check
Git(Hub) Flow
…

31. ContinuousIntegration 101
by Manuel Spezzani
Bologna, October30, 2014