At J and Beyond 2011, I presented a session about using Continuous integration processes during Joomla and PHP development. I present the concepts of CI, and give some direction where to start setting it up yourself.

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

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

12. Faster development

13. Better code management

14. Automated building

16. Version control with regular commits

17. Improve development workflow

18. Reduce risks

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

21. Vital for single developers and large teams

22. Put everything in version control

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

25. Should contain any steps that are repeatable

27. The most difficult aspect to get started with

28. Can test both the code, and browser functionality

30. Can make files available on servers or locally

31. Can be run after a successful 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

43. Begin with version control

44. Put everything under version control

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

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