Continuous Integration and Deployment Patterns for Magento
•
16 likes•6,803 views
Fabrizio Branca (@fbrnc) speaking about "Continuous Integration and Deployment Patterns for Magento" at the Meet Magento Conference 2015 in New York City (#mm15ny)
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (16)
Similar to Continuous Integration and Deployment Patterns for Magento
Similar to Continuous Integration and Deployment Patterns for Magento (20)
More from AOE
More from AOE (20)
Recently uploaded
Recently uploaded (20)
Continuous Integration and Deployment Patterns for Magento
- 1. for Magento
- 5. San Francisco, CA Janine Fiona that’s me Leo
- 6. for Magento = 18.55 slides/min (1 slide every 3.23 sec)
- 16. (and that’s ok…)
- 18. type “YESIKNOWWHATIMDOING” + click automatically
- 19. Continuous Development Continuous Delivery Continuous Integration Continuous Deployment Continuous Monitoring Continuous Jenkins Everything sounds better with “continuous”
- 21. every time you change code passed all tests deployed to production
- 23. One size doesn’t fit all!
- 25. What is it? A simple shell script. That’s it! No Ant, no Phing, no fancy PHP tool/framework Where is it used? In the build job of a Jenkins server What does it need to know? Where to get all the source code from What does it do? add metadata, composer, minify, packaging, upload to S3
- 26. What is it? A couple of chef cookbooks. Run by AWS OpsWorks or Vagrant,… Where is it used? On the target servers What does it need to know? The role of the server (web server, devbox, Redis,…) What does it do? Installing and configuring web server, PHP, MySQL, Redis,…
- 27. What is it? A simple shell script. Or the “deploy” chef cookbook Or EasyDeployWorkflows Where is it used? On the target servers What does it need to know? How to get the build and where to deploy it to What does it do? (Resetting the environment), getting the build, extracting it, managing release folders and symlinks, triggering installer, cleanup old releases
- 28. What is it? A simple shell script. Sometimes triggered inside “deploy” before_migrate.rb Where is it used? On the target servers, called from deployment step What does it need to know? What environment this is. Injected settings What does it do? Run modman, apply settings, trigger update scripts, customize cache prefix, indexing,…
- 29. doesn’t know anything about the app, except where to get it from and where to put it knows how to get the app up and running
- 33. no creating CMS blocks no creating product attributes no updating of any configuration settings! no clearing the cache no purging CDN or Reverse Proxy content!
- 34. media directory (sometimes minified) Database dump (Vanilla) Magento core Modules Scripts Settings Tools
- 35. Urls Database Settings Payment Provider Configuration Feature Flags… Everything that’s different between two environments
- 39. Every file is a potential security risk Don’t deploy anything you don’t need to operate the website
- 42. Use Jenkins to implement a full deployment pipeline for your projects! Test our Open Source Magento modules with Travis CI!
- 45. Vagrant Boxes
- 46. Awesome stuff Every single line potentially can break production! Bratwurst (Germans) Donut (Americans) Pizza (Italians)
- 47. master Feature B Feature A Hotfix (if master is not modified) Hotfix (if master is modified) Feature C build install on integration tests build install on integration tests install on deploy build install on integration tests deploy to stage deploy to prod build install on integration tests deploy to stage deploy to prod build install on integration tests deploy to stage deploy to prod single mainline no commits, only --no-ff merges
- 48. Version Control GIT, SVN,… PHP lint
- 49. Version Control Code Reviews Crucible,…
- 50. Code Reviews Build Files DB Installer Settings Triggered by commits, by time or manually Build job in Jenkins minify js/css .tar.gz “virtual package” (revision)
- 53. Static Code Analysis Install on “Integration” First system where code from all developers/teams meets each other unstable system, might be broken, will be rebuilt without warning
- 55. Unit Tests Integration Tests MPMD broken links, HTTP headers, W3C validity,… Test features that rely on other parts (e.g. framework, external services,…) External components (SSL, Redis, Varnish, ERP, Data Import,…) Basically this is also PHPUnit, but addressing other things
- 56. Integration Tests Acceptance Tests Selenium
- 61. Acceptance Tests Install on “Staging” Behat, PDIFF,… Same setup as production, but different machines Client QA / approval
- 62. Install on “Staging” Stress Tests JMeter Spin up EC2 instances to produce traffic
- 63. Again: multiple servers or autoscaling setup Stress Tests Install on “Production” A/B Deployments on different scales Plan B: rollback Zero Downtime
- 70. Version Control Code Reviews Build Static Code Analysis Install on “Integration” Unit Tests Integration Tests Acceptance Tests Install on “Staging” Install on “Production” Enable Features
- 71. Pipeline Visualization #284 #283 #282 #281 #280 Build Static Code Analysis Unit Tests Install on “Integration” Integration Tests Acceptance Tests #285 for team dashboards
- 73. Tom E.
- 75. Follow me on twitter! My blog