Continuous Delivery from a Developer's Perspective

The nitty gritty.

Transcript

1. C o n t i n u o u s D e l i v e r y from a developers perspective by Hammer Sunday, April 29, 12
2. SAKURA in JAPAN Sunday, April 29, 12
3. HOW LONG does it take you to deploy a 0 POINT STORY? Sunday, April 29, 12
4. CONTINUOUS DELIVERY is about reducing deployment LEAD TIME Sunday, April 29, 12
5. Continuous Delivery Continuous Deployment VERSUS Sunday, April 29, 12
6. Delivery is a BUSINESS decision and not a developer decision Sunday, April 29, 12
7. Developers are responsible for ensuring that master is always DEPLOYABLE Sunday, April 29, 12
8. PATTERNS to ensure master deployability Sunday, April 29, 12
9. Do not PUSH until you are FINISHED Sunday, April 29, 12
10. Create short-lived ad-hoc feature branches Sunday, April 29, 12
11. Change the VIEW LAST MODEL FIRST A N D T H E Sunday, April 29, 12
12. Create short-lived ad-hoc feature toggles Sunday, April 29, 12
13. Create a new ROUTE Sunday, April 29, 12
14. Build a complex production-level feature enablement mechanism like Facebook Sunday, April 29, 12
15. 80 PERCENT of the time we should use DO NOT PUSH UNTIL FINISHED and CREATE FEATURE TOGGLE Sunday, April 29, 12
16. PRODUCT PIPELINES Sunday, April 29, 12
17. DELIVER PIPELINES are how we business VALUE Sunday, April 29, 12
18. DELIVERY organize mechanisms around PRODUCTS Sunday, April 29, 12
19. DEVELOPERS is not EASY for CONTINUOUS DELIVERY Sunday, April 29, 12
20. EXIST? FEATURE TOGGLES how long should Sunday, April 29, 12
21. BUGS? when there are what happens Sunday, April 29, 12
22. DEPLOY? SHOULD we how often Sunday, April 29, 12
23. PRODUCTS? SPLIT when should we Sunday, April 29, 12
24. HANDLED? DEPENDENCIES how are Sunday, April 29, 12
25. SPACE there is for INNOVATION Sunday, April 29, 12
26. QUESTIONS? Sunday, April 29, 12