Continuous Integration (CI) is a software development practice where team members frequently integrate their work, ideally daily, with automated builds to quickly identify integration errors. Key components of CI include version control, build management, self-testing, and deployment, which help in reducing bugs and improving development workflows. To get started with CI, it is recommended to begin with version control and gradually implement automated processes.

1. Continuous Integration (CI) Jeremy Wilken www.gnomeontherun.com @gnomeontherun Lead Developer @ Joomlashack

2. What CI is not A program, tool, or something you install A goal or something that you complete

3. The obligatory definition “ Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test ) to detect integration errors as quickly as possible.” - Martin Fowler with emphasis added

4. My shorter version “ Continuous Integration is a software development process , where members of a team combine and build their code regularly, run automated tests , and distribute a copy of the program for testing or use.” - Adapted from Martin Fowler's definition

5. An example development cycle Team of 5 developers, writing Java

6. Programmed individual parts separately

7. Merged and attempted to compile code

8. Debugging cycle until compiles

9. Product testing and further debugging

10. Product release completed

11. Goals of using a CI process Reduced bugs

12. Faster development

13. Better code management

14. Automated building

15. Unit tests Deployment of files

16. Version control with regular commits

17. Improve development workflow

18. Reduce risks

19. Pillars of CI Version Control Build Management Self Testing Deployment

20. Version Control Manages the source code, tracks changes, merge code changes Examples: Subversion, Git, Mercurial

21. Vital for single developers and large teams

22. Put everything in version control

23. Build Management Build programs compile or integrate the code base of a project, and manage other automated tasks Examples: Phing, Ant

24. You can create custom tasks if they don't exist

25. Should contain any steps that are repeatable

26. Self Testing Running code tests to verify code executes, by testing the parts individually Examples: phpUnit, Selenium

27. The most difficult aspect to get started with

28. Can test both the code, and browser functionality

29. Deployment Making the built program available immediately for testing or use Examples: FTP, SCP, Dropbox

30. Can make files available on servers or locally

31. Can be run after a successful build

32. Code commit or timer triggers build

33. CI server updates to latest code revision

34. CI server starts a new build

35. Build program executes tests and any code analysis, integrates code base into useable form

36. CI server deploys files The basic CI process

37. Example setup for PHP projects Version Control Subversion or Git Build Management Phing Self Testing phpUnit Deployment SCP/FTP/Network Continuous Integration Server Jenkins CI

38. Example setup for PHP projects

39. Example setup for PHP projects

40. Example setup for PHP projects

41. Example setup for PHP projects

42. Getting started with CI Start small, adding new steps slowly

43. Begin with version control

44. Put everything under version control

45. May want automated, can start with manual Setup a build process

46. Use an old computer or virtual machine as server

47. Its a change of mindset, not just tools

48. Add unit tests as you update code

49. Resources Continuous Integration: martinfowler.com/articles/ continuousIntegration.html

50. Jenkins: jenkins-ci.org

51. Phing: phing.info

52. PHPUnit: phpunit.de

53. Jenkins with PHP: jenkins-php.org

54. Questions and Answers Jeremy Wilken www.gnomeontherun.com @gnomeontherun