Continuous delivery - JAX London 2011
•
2 likes•950 views
An overview of the many issues involved in continuous delivery along w
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Continuous delivery - JAX London 2011
Similar to Continuous delivery - JAX London 2011 (20)
More from John Stevenson
More from John Stevenson (20)
Recently uploaded
Recently uploaded (20)
Continuous delivery - JAX London 2011
- 1. Continuous Deployment The writing is on the wall John Stevenson Lean Agile Machine ©LeanAgileMachine Creative Commons Licence
- 2. Who is John Stevenson ● Lean agile coach Kanban, system thinking, ToC. ● Atlassian ambassador in UK Growing communities around JIRA... ● Community geek London Java, Graduate Devs, London Scala, London Clojurians, etc. ● Dabbles with ©LeanAgileMachine Creative Commons Licence
- 3. My Journey ● Started with RUP, UML & XP ● Fell for Behaviour Driven Development & kanban ● Learn about a lot of Value & Systems thinking ● Coached teams & individuals ● Sharing experiences with community ©LeanAgileMachine Creative Commons Licence
- 4. So what is Continuous Deployment ? ©LeanAgileMachine Creative Commons Licence
- 5. ...its incredibly hard ©LeanAgileMachine Creative Commons Licence
- 6. ...even if you are... ©LeanAgileMachine Creative Commons Licence
- 7. ...hard plus infinity for everyone else ©LeanAgileMachine Creative Commons Licence
- 8. Continuous deployment example: ©LeanAgileMachine Creative Commons Licence
- 10. Typically: 25 deploys per day per developer ©LeanAgileMachine Creative Commons Licence
- 12. So why go for continuous deployment? ©LeanAgileMachine Creative Commons Licence
- 17. http://blog.thehigheredcio.com/2011/08/31/efficiency-vs-effectiveness/ ©LeanAgileMachine Creative Commons Licence
- 18. Understanding the business Table stakes / foundations Differentiators Spoilers Accelerators ©LeanAgileMachine Creative Commons Licence
- 21. Where to get started ?? ©LeanAgileMachine Creative Commons Licence
- 22. Is your team / company ready ? A case study in pain and dissapointment! ©LeanAgileMachine Creative Commons Licence
- 23. Change can be expensive ©LeanAgileMachine Creative Commons Licence
- 24. A long journey of discovery ©LeanAgileMachine Creative Commons Licence
- 25. Involving the whole business ©LeanAgileMachine Creative Commons Licence
- 26. Understanding of Value ©LeanAgileMachine Creative Commons Licence
- 27. The right motivation ©LeanAgileMachine Creative Commons Licence
- 28. What is the goal? ©LeanAgileMachine Creative Commons Licence
- 29. Where to start ?? ©LeanAgileMachine Creative Commons Licence
- 30. Visualise how you do IT... ©LeanAgileMachine Creative Commons Licence
- 31. Kanban – a wall of Facts ©LeanAgileMachine Creative Commons Licence
- 32. Let the board show issues... V1.0.1, V1.0.2, V1.0.3, V1.0.4, Build 1209 Build 1221 Build 1301 ©LeanAgileMachine Creative Commons Licence
- 33. Value stream mapping The (often wide) path to getting things done Activities that get things done effectively ©LeanAgileMachine Creative Commons Licence
- 37. Include the whole process... Strategy to shiped Budgeting Business sign off Deployment dry run ©LeanAgileMachine Creative Commons Licence
- 38. Improve the foundations ©LeanAgileMachine Creative Commons Licence
- 39. Monitoring your servers ● Nagios / NagVis ● The Dude ● Microsoft Operations Manager ● Outsource IT... ©LeanAgileMachine Creative Commons Licence
- 45. Sever Provisioning ©LeanAgileMachine Creative Commons Licence
- 46. Its all virtual these days... ©LeanAgileMachine Creative Commons Licence
- 48. Virtual Machines Automate provisioning Manage sys-admin tasks remotely Spin up instances into the cloud Using public cloud when your private cloud is maxed out Off the shelf pre-configured servers ©LeanAgileMachine Creative Commons Licence
- 49. Managing VM's is easy ©LeanAgileMachine Creative Commons Licence
- 50. Automating Virtual Machines ©LeanAgileMachine Creative Commons Licence
- 51. Vagrant – simple to use ● Requirements Ruby Virtualbox Chef / Puppet for other VM systems ©LeanAgileMachine Creative Commons Licence
- 53. Automated server management Puppet / Chef / Rex ©LeanAgileMachine Creative Commons Licence
- 54. Disaster recovery for learning ©LeanAgileMachine Creative Commons Licence
- 55. Change freezes The period of time when the most of the changes happen When lots of patches are done ! A good time to learn what is important ! ©LeanAgileMachine Creative Commons Licence
- 56. Deployment Strategies ©LeanAgileMachine Creative Commons Licence
- 57. If it hurts, do it more often ©LeanAgileMachine Creative Commons Licence
- 58. Segmented deploys Different customers / different expectations ©LeanAgileMachine Creative Commons Licence
- 59. Timely deployments Cost of delay ? When is the software valuable ? ©LeanAgileMachine Creative Commons Licence
- 61. Visualise deployment strategies?? ©LeanAgileMachine Creative Commons Licence
- 62. Managing your code ©LeanAgileMachine Creative Commons Licence
- 63. It compiles, ship it!! Ship It Compile ©LeanAgileMachine Creative Commons Licence
- 64. Automated builds Design around common patterns for building Should have valuable reason for doing something different SBT ©LeanAgileMachine Creative Commons Licence
- 65. Simple Maven config <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.mycompany.app</groupId> <artifactId>my-app</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>Maven Quick Start Archetype</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.8.2</version> <scope>test</scope> </dependency> </dependencies> </project> ©LeanAgileMachine Creative Commons Licence
- 66. Local repositories Nexus Artefactory DVCS ©LeanAgileMachine Creative Commons Licence
- 67. Build tools – continuous feedback Maven 3 Shell Simple Build Tool ~Tests ©LeanAgileMachine Creative Commons Licence
- 68. Coding fast feedback JavaScript ©LeanAgileMachine Creative Commons Licence
- 69. Testable code ● TDD / BDD helped devs have a better appreciation of code that is more testable ● Faster feedback gave devs (and team) better understanding of what is needed ● Resolve issues quickly, prevent many from happening at all ● ©LeanAgileMachine Creative Commons Licence
- 70. Behaviour Driven Developent ©LeanAgileMachine Creative Commons Licence
- 71. Deployable software ● Automated server builds ● Automated deployment scripts / tools ● Automated tests / specifications ● Effective business review ● Faster feedback ● Resolve issues quickly ● Deploy when valuable ©LeanAgileMachine Creative Commons Licence
- 72. Distributed Versioning ● Smaller repositories Per component / module Simpler architecture ● Manage branching easier with pull requests A pull system is more effective than central push ● Different repos for different purposes Repo for deployment, trunk, CI server ©LeanAgileMachine Creative Commons Licence
- 74. Git Workflow ©LeanAgileMachine Creative Commons Licence
- 75. Git architecure (logical) ©LeanAgileMachine Creative Commons Licence
- 79. Code reviews DVCS push requests ©LeanAgileMachine Creative Commons Licence
- 80. Central or Distributed Version control ©LeanAgileMachine Creative Commons Licence
- 82. Centralised issues Fear of breaking the build unnecessary branching delayed commits Off-line support? Any redundancy in versioning server? ©LeanAgileMachine Creative Commons Licence
- 83. Managed Distributed team ©LeanAgileMachine Creative Commons Licence
- 84. Continuous Integration What When How long Run specifications / unit tests Reports Actions to initiate ©LeanAgileMachine Creative Commons Licence
- 85. CI Server basics ©LeanAgileMachine Creative Commons Licence
- 86. BOfH CI Server Kicks out checked in code if it fails Wires up build bunnies to stop you hiding from broken builds Wall of shame for breaking builds Top ten worst programmers ©LeanAgileMachine Creative Commons Licence
- 89. CI Server lights ©LeanAgileMachine Creative Commons Licence
- 91. Issue ticker Stream of issues flowing Highlight new features, overdue items, critical issues, time related news, etc ©LeanAgileMachine Creative Commons Licence
- 93. UltimateWallboard .com ©LeanAgileMachine Creative Commons Licence
- 94. More than compiling code... conf/tomcat-users.xml <user username=”bamboo” password=”bamboo” roles=”manager-script,manager-gui”/> ©LeanAgileMachine Creative Commons Licence
- 95. One click deploy ©LeanAgileMachine Creative Commons Licence
- 96. Architect for deployment Modular systems Simple interfaces Supported by acceptance tests (specifications) Automate low value tasks ©LeanAgileMachine Creative Commons Licence
- 98. Predictability / Cadence Smaller tasks Understanding you capacity ©LeanAgileMachine Creative Commons Licence
- 101. How will you make a change ? ● Automated deployments ● Distributed version control ● Refactoring architecture, design & code ● Modularity in design ● Migrating from technical debt ● Shouting... ©LeanAgileMachine Creative Commons Licence
- 103. Thank you ©LeanAgileMachine Creative Commons Licence
- 104. Feedback & Refs @JR0cket John@jr0cket.co.uk Please note: Very few bulletpoints were hurt during the making of this presentation ©LeanAgileMachine Creative Commons Licence