Continuous Integration in PHP
- 1. LESZEK KRUPIŃSKI PHPERS WARSZAWACONTINUOUS INTEGRATION AND PHP
- 2. HELLO. LESZEK KRUPIŃSKI ARCHITECT CONSULTANT DEVELOPER @LEAFNODELEAFNODE.PL
- 3. MANY PEOPLE DEVELOP THE SAME CODEBASE
- 6. REALITY
- 8. RELEASE!
- 14. METHOD: INTEGRATION EVEN FEW TIMES A DAY
- 15. RULES YES, IT’S FROM WIKIPEDIA
- 18. 3 LET THE BUILD TEST ITSELF
- 19. 4 EVERY DEVELOPER COMMITS TO THE MAIN BRANCH AT LEAST ONCE A DAY
- 20. 5 EVERY COMMIT SHOULD BE BUILT AND TESTED
- 21. 6 BUILD SHOULD BE FAST
- 22. 7 TEST IN PRODUCTION- LIKE ENVIRONMENT (AS CLOSE AS YOU CAN)
- 23. 8 GIVE DEVELOPERS ACCESS TO THE BUILD ARTIFACTS
- 24. 9 EVERY DEVELOPER HAS ACCESS TO THE LAST BUILD RESULTS
- 26. +/-
- 29. MEET JENKINS (SOMETIMES KNOWN AS HUDSON)
- 31. INSTALLATION • Stand-alone JAR • Tomcat • apt-get install jenkins • apache/nginx proxy
- 32. TRIGGERS
- 33. BUT… PHP DOES NOT COMPILE! (SORT OF)
- 35. USING EXTERNAL TOOLS CONNECTORS DYNAMIC DUO: SEBASTIAN BERGMANN STEFAN PRIEBSCH
- 37. SELENIUM
- 38. PHP DEPEND CODE COMPLEXITY AND ERRORS
- 42. CODESNIFFER
- 45. CODE BROWSER
- 46. THAT’S NOT ALL!
- 47. RUNNING SCRIPTS
- 48. DEPLOYMENT
- 49. SLAVE? GIVE ME YOUR KEY.
- 50. ACCESS CONTROL
- 51. LET’S PLAY!
- 54. http://www.pinterest.com/pin/430164201879093032/
- 57. http://www.panic.com/blog/the-panic-status-board/
- 58. WHAT ELSE