From Continuous Integration to DevOps


Published on

Continuous integration has gone mainstream. It has helped development teams move quicker, and has disrupted build management and put additional pressures on deployment groups. In this presentation, we look at how CI achieved such a disruptive, positive impact, how it is turning into Continuous Delivery, and where DevOps fits into the picture (And how DevOps will be just as disruptive).

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • We don’t want them just reading this slide. Less text on slides if we’re presenting.
  • CI is based on the observation that the longer development streams diverge, the more painful the eventual integration will be. Taking the converse of the above statement, the more frequently developers integrate their changes, the more painless those integrations will be
  • It’s arguably the most important test. Non-compiling code, really hurts the rest of your team
  • From Continuous Integration to DevOps

    1. 1. From Continuous Integration to DevOps<br />
    2. 2. Maciej Zawadzki<br />Cofounder and CEO of Urbancode<br />Original author of AnthillPro. Architect of Urbancode’sDevOps Platform.<br />Blog:<br />Twitter: @devl_in_details<br />
    3. 3. Eric Minick<br />Lead Consultant<br />Worked as a dev, tester, and release guy<br />Dozens of enterprise rollouts <br />Blog:<br />Twitter: @EricMinick<br />
    4. 4. Agenda<br />Continuous Integration<br />Continuous Delivery<br />DevOps<br />The Future<br />Resources<br />
    5. 5. CI: it’s about Quality Determination<br />CI is based on the observation that the longer development streams diverge, the more painful the eventual integration will be. Taking the converse of the above statement, the more frequently developers integrate their changes, the more painless those integrations will be.<br />But, why does it not suffice for developers to simply check-in or commit their changes frequently to practice CI? <br />Implied condition -- that each integration will not decrease the code quality. This is the key to understanding CI; the rest is implementation details.<br />
    6. 6. CI: it’s about Quality Determination<br />Integrating frequently is less painful than infrequently.<br />But, If we commit frequently blindly, we have a broken code base<br />Implied condition: each integration will not decrease the code quality. <br />This is the key to CI <br />The rest is implementation details.<br /><br />
    7. 7. CI: the Implemention<br />How do we determine code quality? We test it<br />How do we test code? We build it and run tests against it<br />CI requires fast feedback, so what tests do we run? Unit tests<br />This is how we get from CI to CI servers and software builds<br />
    8. 8. CI: the Disruption of Build Management<br />Paradigm change: similar to structure of scientific revolutions – Thomas Kuhn<br />Before CI, build engineers would:<br />Manually perform the build<br />After the paradigm change, build engineers would:<br />Design the build process for projects. The actual build execution is handled by a tool.<br />
    9. 9. CI: the Bumps<br />CI Builds<br />Purpose: determine quality of latest changes<br />Audience: development team<br />Source: Build is traceable to latest changes and “latest” source<br />Artifacts: Throw away builds, tests are important<br />Build Management Builds<br />Purpose: produce artifacts for 3rd parties<br />Audience: 3rd parties outside development<br />Source: Build is traceable to source<br />Artifacts: Important builds, artifacts are important and primary<br />
    10. 10. CI: the Innovation of Automation<br />Invention: proven to work in the laboratory<br />Innovation: it can be replicated reliably on a meaningful scale at practical costs.<br />For an idea to move from invention to innovation requires an ensemble of critical components. Peter M. Senge, The Fifth Discipline<br />CI brings together “critical” factors:<br />Automation<br />Self-service<br />Transparency/Visibility<br />
    11. 11. CI: Summary<br />CI requires the determination of code quality<br />CI disrupted Build Management<br />CI represents the Innovation of Automation<br />
    12. 12. Agenda<br />Continuous Integration<br />Continuous Delivery<br />DevOps<br />The Future<br />Resources<br />
    13. 13. Continuous Delivery: What is it?<br />Continuation of the Quality Determination that CI started.<br />Functional tests require deployment.<br />Progression through environments on a march to production, with “the build” subjected to more exhaustive tests in each environment.<br />
    14. 14. Continuous Delivery: The Drivers<br />Quality Determination:<br />CI left unfinished business on the table.<br />Further tests require deployments.<br />Agile: keeping up with the pace. <br />Innovation of Automation: self-service and visibility have a powerful attraction<br />
    15. 15. Continuous Delivery: the Details<br />Deploying multi-tiered applications is not trivial. <br />Application model<br />Component (tier) model<br />Mapping of components to servers in each Env.<br />Multiple Tiers<br />Database changes<br />Middleware code changes<br />Middleware config changes<br />Flat file changes<br />Multi-environment deployments<br />Handle different environment topologies<br />Handle different environment configurations<br />
    16. 16. Continuous Delivery & Mountain Bikes<br />How many people own a mountain bike?<br />How many people ever took it down a mountain?<br />The guys that deploy to production 50 times a day drive their mountain bike down the mountain.<br />The rest of us benefit from the technology as we have a comfortable ride on the park trails with our kids.<br />
    17. 17. Continuous Delivery: Theory & Reality<br />The reality is that:<br />Dev and Ops are in different silos<br />Dev and Ops use different tools<br />Dev produces change, Ops seeks to control change<br />50 page Word doc is the standard hand-off between Dev and Ops<br />
    18. 18. Continuous Delivery: Summary<br />CD follows through on what CI started, the quality determination<br />CD is enabling technology for deployments<br />CD reality is that most organizations use it in lower environments only<br />
    19. 19. Agenda<br />Continuous Integration<br />Continuous Delivery<br />DevOps<br />The Future<br />Resources<br />
    20. 20. DevOps: the Drivers<br />The Cloud (IaaS): <br />Has all the “critical” factors for Innovation<br />Self-service is a radical shift in the SLA<br />Hand-off document leads to errors<br />Agile leads to faster pace<br />
    21. 21. DevOps: the Disruption<br />Cloud offers an alternative to Enterprise IT<br />Enterprise IT will need to match the SLA<br />Private cloud under Enterprise IT control is a way to remain competitive<br />Adopting cloud automation is a paradigm shift for Enterprise IT<br />Once the paradigm shifts, the flood gates open for deployment automation<br />
    22. 22. DevOps: the Implementation, Convergence<br />IaaS on a private cloud<br />Environment provisioning as a service.<br />Application teams may request environments for their applications. <br />Environments come pre-configured with DB and middleware. <br />Application Deployment (CD) to provisioned environments.<br />
    23. 23. DevOps: the Bumps Ahead<br />Dev<br />Ops<br />Very High Tempo<br />Can rebuild database / app from scratch<br />No need for Rollbacks<br />Audit is nice to have<br />Security, traceability, separation of duties.<br />New Environments are common<br />Slower Tempo<br />Incremental updates to Database and App<br />Rollbacks are huge<br />Audit Critical<br />Security, traceability, separation of duties.<br />New environments are<br /> rare<br />
    24. 24. The Summary<br />CI represents Innovation of Automation<br />CI got us started down the road towards PROD<br />CD continued the work that CI started <br />CD provided enabling technology for application deployments<br />DevOps will disrupt Ops the same way CI disrupted Build Management<br />DevOps opens the door for the convergence with Dev practices such as CD<br />
    25. 25. Agenda<br />Continuous Integration<br />Continuous Delivery<br />DevOps<br />The Future<br />Resources<br />
    26. 26. Where are we headed?<br />Private clouds (or public/private)<br />Platform as a service<br />Servers with middleware, properly configured, managed, and available self-service.<br />Application deployment onto the platform<br />Release Management<br />Tracks builds through the (PaaS) environments from CI to Production. <br />Same deployment process for all environments<br />
    27. 27. Where are the tools headed?<br />Pre-2006: Just CI tools<br />2006-2010: CI becomes Continuous Delivery <br />First end-to-end tool is AnthillPro in 2006. <br />Now: DevOps<br />CI is commodity.<br />Integrated CD tools focus on point solutions deployment and pipeline management. <br />Expanding integrations with private cloud<br />
    28. 28. Agenda<br />Continuous Integration<br />Continuous Delivery<br />DevOps<br />The Future<br />Resources<br />
    29. 29. More on CI, CD, and DevOps<br />Webinars and more:<br />Death to Manual Deployments!<br />Build & Deployment Automation for the Lean Economy<br />Enterprise DevOps: Scaling Build, Deploy, Test, Release<br />You should follow us:<br /><br /><br /><br />
    30. 30. Yes, UrbanCode sells Agile / DevOps tools<br />AnthillPro is now the DevOps Platform<br />DevOps Platform<br />Automated build, test and deployment. Includes UrbanDeploy. <br />UrbanDeploy<br />Deployment and release management<br />
    31. 31. Questions?<br />Or ask us later:<br /><br />