Con2nuous	  Delivery	         	     Tales	  from	  the	  wild	  
@nigelfds	     github.com/nigelfds	  
Great	  Message!	  We	  shall	  do	  Con2nuous	  Delivery	  
Really	  difficult	  execu2on	  
Silver	  Bullet	  Syndrome	  
Its	  about	  Risk	  
“I	  do	  believe	  that	  complexity	  is	  the	  enemy.	  Un7l	  we	  be9er	  understand	  complexity,	  our	  chances	 ...
Deployment	  	                        v	  	  Configura2on	  Management	  	                        v	          	  Test	  Aut...
Single	  Stream	  
Mul2-­‐team/Mul2-­‐stream	  
Op2mum	  condi2ons	  
Cycle	  2me	  
Batch	  size	  
Stability	  
High	  value	  
Sounds	  crazy?	  
It	  already	  exists	  in	  your	  company	  
They	  just	  call	  it	  
Ar2fact	                   Test	                      Staging	                  Prod	                BAU	               Tr...
The	  pit	  stop	  crew	  is	  king	  
Keep	  the	  turn	  around	  2me	  low	  
Ar2fact	                   Test	                                Staging	                  Prod	                           ...
Keep	  the	  path	  to	  produc2on	  clear	  
Ar2fact	                         Test	                           Staging	                  Prod	               Trunk	     ...
Encourage	  the	  right	  behaviors	  
Pressure	  on	  longer	  cycles	  to	       merge	  more	  o`en	  
Pressure	  to	  keep	  batch	  size	  small	  
Pressure	  to	  release	  more	  o`en	  	                       	  
Summary	  
This	  stuff	  is	  hard	  to	  get	  right	  
A	  great	  place	  to	  start	  is	  the	  produc2on	  support	  line	  
Thank	  you	  
DevOps Days Melbourne meet-up
Upcoming SlideShare
Loading in …5
×

DevOps Days Melbourne meet-up

1,232 views
1,165 views

Published on

This is a talk I gave at the DevOps days meet-up in Melbourne in June 2012.

In the talk I go over implementing Continuous Delivery in an enterprise organisation. Its based on our experiences doing CD in a large traditional Telco in Australia.

It covers:
- an introduction to the principle
- the state of the art of Cont. Delivery in Single application versus multistream development
- the optimum conditions to start implementing and measuring CD
- focusing on the BAU/Support line as an entry point

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,232
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
11
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

DevOps Days Melbourne meet-up

  1. 1. Con2nuous  Delivery     Tales  from  the  wild  
  2. 2. @nigelfds   github.com/nigelfds  
  3. 3. Great  Message!  We  shall  do  Con2nuous  Delivery  
  4. 4. Really  difficult  execu2on  
  5. 5. Silver  Bullet  Syndrome  
  6. 6. Its  about  Risk  
  7. 7. “I  do  believe  that  complexity  is  the  enemy.  Un7l  we  be9er  understand  complexity,  our  chances  of  building  be9er  IT  systems  is  limited.  The  first  thing  we  must  understand  about  complexity  is  that  not  all  complexity  is  equal.  And  the  complexity  on  which  most  people  focus  is  probably  the  least  complex  complexity  of  all.”  Roger  Sessions   hHp://simplearchitectures.blogspot.com/2009/03/cancer-­‐of-­‐complexity.html  
  8. 8. Deployment     v    Configura2on  Management     v    Test  Automa2on    
  9. 9. Single  Stream  
  10. 10. Mul2-­‐team/Mul2-­‐stream  
  11. 11. Op2mum  condi2ons  
  12. 12. Cycle  2me  
  13. 13. Batch  size  
  14. 14. Stability  
  15. 15. High  value  
  16. 16. Sounds  crazy?  
  17. 17. It  already  exists  in  your  company  
  18. 18. They  just  call  it  
  19. 19. Ar2fact   Test   Staging   Prod   BAU   Trunk   Ar2fact   Merge  with    VCS   Test   Test   Trunk   Tac2cal   Ar2fact   Test   Test   Merge  with     Trunk   Programme  
  20. 20. The  pit  stop  crew  is  king  
  21. 21. Keep  the  turn  around  2me  low  
  22. 22. Ar2fact   Test   Staging   Prod   1  DAY   Trunk   Ar2fact   Merge  with    VCS   Test   Test   Trunk   2  WEEKS   Tac2cal   Ar2fact   Test   Test   Merge  with     Trunk   Programme   3  MONTHS  
  23. 23. Keep  the  path  to  produc2on  clear  
  24. 24. Ar2fact   Test   Staging   Prod   Trunk   8  hours  then  back-­‐out   Ar2fact   Merge  with    VCS   Test   Test   Trunk   Tac2cal   Ar2fact   Test   Test   Merge  with     Trunk   Programme  
  25. 25. Encourage  the  right  behaviors  
  26. 26. Pressure  on  longer  cycles  to   merge  more  o`en  
  27. 27. Pressure  to  keep  batch  size  small  
  28. 28. Pressure  to  release  more  o`en      
  29. 29. Summary  
  30. 30. This  stuff  is  hard  to  get  right  
  31. 31. A  great  place  to  start  is  the  produc2on  support  line  
  32. 32. Thank  you  

×