CI
1 like342 views
Continuous Integration (CI) is a software development practice where developers regularly merge their work into a central repository. This allows for automated builds and tests which catch errors early. CI helps reduce integration problems, improves code quality, and allows for more frequent deployments. The document discusses implementing CI with tools like Jenkins, build scripts, unit testing, code analysis, and notifications to improve the development process.
CI
- 1. Continuous Integration Stop procrastinating and build often!
- 2. Who am I? Patrick Mizer Chief Architect at SpareFoot ZCE: PHP4, PHP5, and ZF patrick@sparefoot.com github.com/maximizer
- 3. We help consumers search, compare, and book self storage online. Im not supposed to say this but Think Hotels.com, but for self storage.
- 4. We have been using a Continuous Integration workflow since 2009
- 5. SpareFoot in 2009 20 Visits per day 1 RackSpace cloud instance 2 Developers 1 Application 5-10 builds per day Deployed whenever -> % svn up
- 6. SpareFoot Today 2 million visitors per month > 50 AWS EC2 instances 35 developers 7 product teams. 100-200 builds per day Continuous Delivery
- 7. What I will cover... What is CI? Why do it? The Jenkins CI Server What does a CI workflow look like? Build Tools Testing and Analysis Notification Lessons Learned
- 8. I want to clarify something..
- 9. Continuous something... Continuous Integration Continuous Delivery Continuous Deployment
- 11. Continuous something... Version Control Deploy to Staging Automated Tests AUTO AUTO Continuous Integration Continuous Delivery Continuous Deployment
- 12. Continuous something... Version Control Deploy to Staging Automated Tests Acceptance Tests Deploy to Production AUTO AUTO AUTO MANUAL Version Control Deploy to Staging Automated Tests AUTO AUTO Continuous Integration Continuous Delivery Continuous Deployment
- 13. Continuous something... Version Control Deploy to Staging Automated Tests Acceptance Tests Deploy to Production AUTO AUTO AUTO AUTO Version Control Deploy to Staging Automated Tests Acceptance Tests Deploy to Production AUTO AUTO AUTO MANUAL Version Control Deploy to Staging Automated Tests AUTO AUTO Continuous Integration Continuous Delivery Continuous Deployment
- 14. Continuous something... Version Control Deploy to Staging Automated Tests Acceptance Tests Deploy to Production AUTO AUTO AUTO AUTO Version Control Deploy to Staging Automated Tests Acceptance Tests Deploy to Production AUTO AUTO AUTO MANUAL Version Control Deploy to Staging Automated Tests AUTO AUTO Continuous Integration Continuous Delivery Continuous Deployment
- 15. What is Continuous Integration? CI is a software development process in which developers integrate their work frequently. Each integration is built and verified by automated tests so that errors and inconsistencies are detected and fixed as quickly as possible.
- 16. What is Continuous Integration? CI originated with Extreme Programming CI is a process. It dictates no specific tooling.
- 17. So, why do it?
- 18. So, why do it?
- 19. Finding bugs late is costly Local Development Staging Production Developers QA & Stakeholders Your Customers
- 20. Finding bugs late is costly
- 21. Integration Hell Your changes to the booking service are incompatible with mine. How do we merge now? When did we start using Guzzle 2.0? The SDK requires 3.0 and composer wont let us use both!
- 22. Integration Hell Mainline Developer C Developer A Developer B
- 23. Integration Hell Mainline Developer C Developer A Developer B
- 24. Integration Hell Mainline Developer C Developer A Developer B
- 25. Integration Hell Mainline Developer C Developer A Developer B
- 26. Integration Hell Mainline Developer C Developer A Developer B
- 27. Integration Hell Mainline Developer C Developer A Developer B
- 28. Poor Quality Codebase Who the #$@# is using tabs instead of spaces!? We have 2 classes doing the exact same thing
- 29. Poor Project Visibility What is our test coverage? How is our app performing?
- 30. No Deployable Code It works on my machine! I dont know why its not working on staging, sounds like an ops problem. We need to push a fix for this immediately.
- 31. CI attempts to mitigate these Finding bugs late is costly Integration hell Poor quality code base Poor project visibility No deployable code
- 32. Better code, faster development Better code Code is tested early and often Standards enforced on every commit
- 33. Better code, faster development Better code Code is tested early and often Standards enforced on every commit Faster development Integration issues are found earlier Testing becomes part of everyones process Building is a non-event
- 34. Continuous Integration Implementing a CI solution is pretty straightforward.
- 35. Continuous Integration Maintain an SCM code repository
- 36. Continuous Integration Maintain an SCM code repository Create and automate the build
- 37. Continuous Integration Maintain an SCM code repository Create and automate the build Everyone commits to mainline (at least daily)
- 38. Continuous Integration Maintain an SCM code repository Create and automate the build Everyone commits to mainline (at least daily) Every commit to mainline is built
- 39. Continuous Integration Maintain an SCM code repository Create and automate the build Everyone commits to mainline (at least daily) Every commit to mainline is built Tests verified on a prod-like environment
- 40. Continuous Integration Maintain an SCM code repository Create and automate the build Everyone commits to mainline (at least daily) Every commit to mainline is built Tests verified on a prod-like environment Notify everyone of the results
- 41. Excuses We're not big enough Too much work We don't have devops We don't have tests
- 42. The CI Server Polls for changes Manages and monitors builds Notifies team of results
- 43. Jenkins Free Open Source (MIT License) Built on Java Fork of Hudson Plugins for everything Lots of resources Easy to get going: % sudo apt-get install jenkins % sudo apt-get install jenkins-cli
- 44. Jenkins-php.org Jenkins template for PHP projects put together by Sebastian (yes, that Sebastian) Bergmann Step-by-step Instructions: Template w/ plugins Build file Log formats Jenkins config
- 45. The CI workflow Developer commits code CI Server polls SCM for changes CI Server integrates and builds code to the Integration Environment CI notifies team of result
- 51. The Build Build dependencies Tests Static analysis Artifacts (docs, phar, etc) ...
- 52. Build tools...
- 53. Build tools... But build files are only for compiling.
- 54. Build tools... Use a proper built tool Apache Ant (Java) Phing (PHP)
- 55. Apache Ant build.xml Targets and depends Java = threads ++
- 56. Anatomy of build.xml <?xml version="1.0" encoding="UTF-8"?> <project name="some-php-project" default="build"> <target name="build" depends="phpunit"/> <target name="phpunit" description="Run unit tests"> <exec executable="phpunit" failonerror="true"/> </target> </project>
- 57. SCM polling and build
- 58. The Integration Machine A reasonable facsimile of production Every commit is built here By yourself? Use Vagrant
- 59. Verifying the Build Unit Tests Functional Tests
- 60. Selenium But setting up selenium is hard...
- 61. SauceLabs
- 62. SauceLabs
- 63. Testing is just the beginning
- 64. Static Analysis Analysis of software without actually executing the code.
- 65. Check your PHP syntax PHP Lint php -l foo.php find . -name *.php -exec php -l {};
- 66. PHP Lint
- 67. Coding Standards PHP Code Sniffer phpcs --standard=pear foo.php
- 68. PHP Code Sniffer
- 69. DRY Copy page detector phpcpd -min-lines=5 /src/service/*
- 71. Performance
- 72. Performance - Bonus Phantomjs is a headless browser based on Webkit with JS API YSlow is a tool that analyzes web pages and why theyre slow based on Yahoos rules. Phantomjs + YSlow = Awesomeness
- 73. Performance - Bonus phantomjs yslow.js -i grade -threshold "A" -f junit http://staging.sparefoot.com > results.xml
- 74. Notification
- 75. Notification
- 76. Notification
- 77. Notification
- 78. Lessons Learned
- 79. Lessons Learned
- 80. Lessons Learned Version all of you CI Config. We didnt and now were going back and rewriting it.
- 81. Lessons Learned Building the DB Put your schema changes under version control. Incorporate them into the build Fail when theres a problem. Make this the only way to get schema changes to production.
- 82. Git feature branching Git feature branching solves a separate problem.
- 83. Git feature branching Master Branch C Branch A Branch B
- 84. Our Git Workflow commit commit PUSH Branch Merge Pull request commit PUSHcommit commit commit Merge Pull request MASTER BRANCH B BRANCH A Branch + master built to dev environment and tested. Branch + master built to dev environment and tested. Master built to staging environment and tested.
- 85. Play with Jenkins today! github.com/ maximizer/vagrant-ci % git clone github.com/maximizer/vagrant-ci.git % vagrant up http://localhost:8282 http://jenkins-php.org