High Stakes Continuous Delivery in the Real World #OpenWest

You have a robust set of tests and you're using a continuous integration server, so you feel great about your project. You're ready for the next step - continuous delivery. Automatically deploying your changes to production can be a scary prospect for many teams, but in this talk we'll look at some real world examples in high stakes situations where continuous delivery allows teams to move faster and have greater confidence in their code. We'll walk through a sample CI/CD setup used on a real-world PHP-based ecommerce site and show how you can use this setup for your projects.

Transcript

1. High Stakes Continuous Delivery in the Real World Presented by Joshua Warren
2. OR:
3. How I Learned To Stop Worrying and Love Deployments
5. About Me
6. PHP Developer Working with PHP since 1999
7. Founder & CEO Founded Creatuity in 2008 PHP Development Firm Focused on the Magento platform Some of our developers, October ‘12
8. Frequent Conference Presenter Occasional Open Source Contributor Over-Tweeter
9. JoshuaWarren.com @JoshuaSWarren
10. IMPORTANT! • joind.in/13900 • Download slides • Post comments • Leave a rating!
11. What’s That? CONTINUOUS DELIVERY
12. –ContinuousDelivery.com “Releasing high quality software fast through build, test and deployment automation.”
13. Testing + Automation Increases confidence in completed code Decreases delay between task completion & deployment
14. #OpenWest Continuous delivery is a mindset, not a technology.
15. Any code you commit may be released to customers at any point.
17. Yes, any code you commit may be released to customers at any point.
18. Commits made by Google’s Customer Surveys team are live in production in just 8 minutes.
19. Or: The Benefits of Continuous Delivery WHY WOULD YOU DO THAT?!
20. Frequent feedback from end-users
21. Business advantages - reduce time to market, react to changes faster
22. Efficient Developers focus on developing, not deploying
23. Or: How to Implement Continuous Delivery for PHP Projects OK, YOU’VE CONVINCED US…
24. Prerequisites • Automated testing • Authority to change processes
25. #OpenWest Make your workflow and process changes before beginning to implement a continuous delivery system.
26. Change Your Workflow Today
27. Our Workflow at Creatuity
28. Each branch should be a self-contained new feature
29. When work is complete on a branch, that branch must be completely ready to deploy
30. Completed branch is tested by our continuous integration server
31. Completed branch is tested by our QA team
32. Branch is indicated as deploy-ready
33. Branch is deployed to production
34. CI Server • Bamboo, Jenkins or ? - choice is yours • Our examples will use Bamboo
35. Bamboo Testing • Configure it to your liking • We use phing, phpunit, etc • Must define an artifact, but can be empty
36. Bamboo Deployments • Create a deployment project • Define an environment - in our case, ‘Staging’ • Attach it to your build plan used for testing
38. Bamboo Environments • Environments are just labels • Environment-specific details will be stored elsewhere
40. Bamboo Tasks • Tasks are where the magic happens • We use tasks to trigger our deployment system, rocketeer
42. For now, it’s a magic box… What’s Rocketeer?
44. But we’ll learn more in a bit… Yup, a magic box
45. Rocketeer Check Task rocketeer check --on-staging -n
46. Rocketeer Deploy Task rocketeer deploy —on-staging -n
47. #OpenWest Four short tasks in Bamboo are all it takes to automate deploying your PHP projects.
48. Bamboo Triggers Deploys are triggered on schedule or after every passing build
49. Bamboo Notifications We trigger HipChat notification on every deploy start & finish
50. Each Successful Build Results in an Automatic Deployment
51. Deployments are reported to HipChat, appear on the deployment board in Bamboo
53. JIRA Integration Include JIRA issue keys in your commit message
54. #OpenWest Bamboo + Rocketeer takes us from passed test to deployment in less than half an hour with no manual steps.
55. The magic behind our automatic deployments ROCKETEER
57. Not That Rocketeer github.com/rocketeers/rocketeer rocketeer.autopergamene.eu
58. Rocketeer is a modern PHP task runner and deployment package.
59. Install Rocketeer wget http://rocketeer.autopergamene.eu/versions/rocketeer.phar chmod +x rocketeer.phar mv rocketeer.phar /usr/local/bin/rocketeer
60. Configure Rocketeer cd <checked out copy of your codebase> rocketeer ignite
61. Rocketeer adds a .rocketeer folder to your project Commit this folder
62. Committing .rocketeer allows Bamboo plus anyone on your team to run deployments
63. ‘rocketeer ignite’ will configure most of it’s files for you
64. We’ll modify a few of the files for project-specific details
65. Don’t worry…
66. .rocketeer/config.php Edit host record if you’re using a non-standard SSH port
67. .rocketeer/hooks.php • Add project-specific commands • We’ll add a few Magento-specific items
68. .rocketeer/hooks.php 'before' => [ 'setup' => [], 'deploy' => array( 'magerun sys:maintenance --on' ), 'cleanup' => [], ],
69. .rocketeer/hooks.php 'after' => [ 'setup' => [], 'deploy' => [], 'cleanup' => array( 'magerun sys:setup:run', 'magerun cache:clean', 'magerun cache:flush', 'magerun index:reindex:all', 'magerun sys:maintenance --off', ), ],
70. .rocketeer/remote.php 'shared' => [ 'media', 'var', 'app/etc/local.xml', ],
71. .rocketeer/strategies.php return $composer->install([], ['--no-interaction' => null, ’--no-dev' => null, '--prefer-dist' => null, '--no-plugins' => null]);
72. Next Up • Commit these changes to your Rocketeer files • Prepare your server to receive the deployment
73. Server File Structure • current • releases • shared
74. File Structure • current and releases are managed by Rocketeer • shared contains folders shared by each release
75. Magento Shared Files • app/etc/local.xml • media • var
76. Rocketeer Folder Structure • Rocketeer deploys to a new folder under releases • Updates symlinks to shared folder • Then updates current symlink to new release
77. Rocketeer Prep • Make sure SSH keys are setup correctly • Rocketeer will connect to your SSH repo via your server - before running deploy for the first time, test your SSH setup
78. SSH config file Host yourGitServer.example HostName yourGitServer.example IdentityFile ~/.ssh/your_public_key_rsa IdentitiesOnly yes
79. Rocketeer Prep • rocketeer check • rocketeer deploy —pretend • That’s it - you’re ready to deploy!
81. Or: What’s Next? WHERE DO WE GO FROM HERE?
82. Advanced Rocketeering • Custom tasks • Listening to events, firing events • Task builder • Task queues
83. Feature Toggles • First step of implementing a new feature - wrap it in a feature toggle • Code only executes if feature is enabled • Enables deploying new code immediately
84. Canaries • Deploy to a small portion of your site’s traffic • Compare error rates between new & old version • If error rate is same or lower, deploy globally
85. Don’t get distracted by these advanced concepts - start by moving to basic continuous delivery first.
86. Keep In Touch! • joind.in/13900 • @JoshuaSWarren • JoshuaWarren.com