Ignite Talk: Continuous Delivery: Why Everyone Should Do It
Download as PPTX, PDF•1 like•462 views
The document discusses continuous delivery and why everyone should adopt it. It promotes releasing new features on a frequent basis, such as weekly, daily or even hourly. This allows companies to get ideas to customers much faster, within the same day. The document also lists the pillars of continuous delivery as product, people and process, and emphasizes automating releases, getting early user feedback, and implementing smaller, more frequent release cycles.
Ignite Talk: Continuous Delivery: Why Everyone Should Do It
- 2. Sergiu Bodiu Continuous Delivery: why everyone should do it
- 3. Continuous Delivery: why everyone should do it Sergiu Bodiu Platform Architecture @sergiu_bodiu
- 4. © Copyright 2015 Pivotal. All rights reserved. Can you release NEW features every WEEK every DAY every HOUR
- 5. From idea to production: 6-9 months
- 6. © Copyright 2015 Pivotal. All rights reserved. The Value of Going Fast
- 8. An idea in the morning, is running in production by evening https://www.wealthfront.com/engineering
- 9. © Copyright 2015 Pivotal. All rights reserved. Hire Someone Else 1st task for Labs project: Build the CI/CD Pipeline
- 10. © Copyright 2015 Pivotal. All rights reserved. Learn, Read Books The Three Ways, according to Gene Kim
- 11. © Copyright 2015 Pivotal. All rights reserved.
- 12. © Copyright 2015 Pivotal. All rights reserved.
- 13. © Copyright 2015 Pivotal. All rights reserved.
- 14. © Copyright 2015 Pivotal. All rights reserved.
- 15. © Copyright 2015 Pivotal. All rights reserved.
- 16. © Copyright 2015 Pivotal. All rights reserved. –Merging dev work with mainline trunk constantly to test changes independently and with other changes –Build server automated unit tests Continuous Integration
- 17. ‹#›© Copyright 2015 Pivotal Software. All rights reserved. Pillars of Continuous Delivery Product • Automate app provisioning, deployment and release • Integrate tools across Development and Operations People • Involve early adopters for feedback and initial success • Use success stories to motivate the doubters Process • Reduce or eliminate manual steps in the release process • Implement smaller, frequent release cycles
- 18. © Copyright 2015 Pivotal. All rights reserved. Iterate
- 19. © Copyright 2015 Pivotal. All rights reserved. Pivotal Way
- 20. © Copyright 2015 Pivotal. All rights reserved. This day will never come AGAIN
- 21. © Copyright 2015 Pivotal. All rights reserved. Here is my source code Run it on the cloud for me I do not care how
- 22. © Copyright 2015 Pivotal. All rights reserved.
Editor's Notes
- #4: Resting slide on screen before you begin presenting.
- #6: Do new developers deploy code on their first day, or even during job interviews? Can you sleep soundly after a new hire’s deployment knowing your applications are all running fine?
- #9: Do you practice software development with tools, process and culture that can respond to the speed of market? By contrast you have the early innovators who have fully embraced and adopted an approach to software where There is no release cycle there is just a deploy button A financial Wealth management company (Wealthfront in this case) proudly publishes on their external webpage how often they push code to production. Wealthfront was founded in 2011 and now manages $2.5b and uses software as a competitive advantage Do you practice software development with tools, process and culture that can respond to the speed of market? Do new developers deploy code on their first day, or even during job interviews? An important and in-demand resource these days – Your developers. This is what they really want