Introducing Continuous Delivery in the Enterprise

562 views

Published on

Slides from the "Introducing Continuous Delivery in the Enterprise" webinar on 08 May 2013, 10 GMT/11 CET.

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

No Downloads
Views
Total views
562
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Introducing Continuous Delivery in the Enterprise

  1. 1. Introducing  Con-nuous  Delivery  in  the  Enterprise  Andrew  Phillips,  XebiaLabs  
  2. 2. Andrew Phillipso VP Product Mangement for XebiaLabso Lots of enterprise software development onhigh-performance systemso Been on both sides of the “Dev…Ops” fenceo Active open source contributor and committer:jclouds, Multiverse, Gradle and otherso Cloud, PaaS & JVM language fan (esp. Scala, Clojure)o Regular meetup, conference etc. presenterA Bit About Me…
  3. 3. Our flagship product, Deployit, is a market-leadingApplication Release Automation platform.o  Headquartered in Boston, Massachusettso  Global development and support offices inUS, NL, UK, France and IndiaAbout XebiaLabsBenefits include:o  Reduce development applications costso  Accelerate application time to marketo  Bridge the gap between Development and Operations
  4. 4. o 1min on Continuous Integrationo Continuous Delivery in a Nutshello Enterprise Challenges to CDo A Continuous Delivery Automation Platformo 5 Steps Towards Continuous Deliveryo Convincing Your ManagementAgenda
  5. 5. o  Emerged at the end of the 90s as oneof the XP practiceso  By continuously building and testingsoftware quality should improveo  Tests often limited to unit tests (e.g.JUnit)o  Sometimes also functional tests (e.g.Selenium)The 1min Continuous Integration Intro
  6. 6. o  Emerged at the end of the 90s as oneof the XP practiceso  By continuously building and testingsoftware quality should improveo  Tests often limited to unit tests (e.g.JUnit)o  Sometimes also functional tests (e.g.Selenium)The 1min Continuous Integration Intro
  7. 7. Beyond CIo  Deployment to the target platformoften not part of the CI cycleo  Deployment procedures not tested!o  Application not tested on ultimatetarget platform!
  8. 8. Beyond CIo  Principle #1 of the Agile Manifesto:“Our highest priority is to satisfy thecustomer through early and continuousdelivery of valuable software.”o  What is the business value of code sittingin your repository?
  9. 9. Enter Continuous Delivery
  10. 10. Enter Continuous Delivery
  11. 11. Enter Continuous Deliveryo  Full-scale implementation: Every(tagged) version goes to productiono  Ramping up: Include deployment inthe CI cycle to test the deployedartifacts on the target platform
  12. 12. Enter Continuous Deliveryo  Smoke testso  Landing pageo  Line of Lifeo  Functional tests on target platform (e.g. Selenium)o  Content of the landing pageo  Typical runo  Performance tests (e.g. JMeter)o  Response time of the landing pageo  Response time of the simple / complex path
  13. 13. Enter Continuous Delivery
  14. 14. Enterprise Challengeso  Organizing many jobso  Standardizing common job parameterso  Identifying job ownershipo  Securing job accesso  Automating job sequenceo  Setting up job gates/conditions
  15. 15. Enterprise Challengeso  Same pipeline setup across middleware and OStypeso  Same pipeline setup in private/hybrid cloud andPaaS environmentso  On-demand environment provisioningo  Release Management integrationo  End-to-end “paper trail”
  16. 16. A Continuous Delivery Automation PlatformCloud/Virtualization ProvidersEnvironment ProvisioningContinuousIntegrationDeployitDeployment AutomationBuild Test AutomationRuntime ControlIT Ops AnalyticsRelease CoordinationQuality &MonitoringFeature Delivery
  17. 17. A Continuous Delivery Automation PlatformEC2, vSphere etc.Puppet EnterpriseJenkins EnterpriseDEV@cloudDeployit
  18. 18. Sample Delivery Pipeline
  19. 19. Sample Delivery Pipeline
  20. 20. Sample Delivery Pipeline: Recapo  Enterprise features:o  Folderso  Templateso  Access-controlo  Job gateso  Validated mergeo  “Smart” deployment automationo  “Smart” environment provisioningo  Key ingredient: automated tests!
  21. 21. 5 Steps Towards Continuous Delivery1.  Define extent and branches of pipelineo  Doesn’t have to be Prod straight away!
  22. 22. 5 Steps Towards Continuous Delivery1.  Define extent and branches of pipelineo  Doesn’t have to be Prod straight away!2.  Define triggers and gates for your pipeline phaseso  How many of these can you automate?
  23. 23. 5 Steps Towards Continuous Delivery1.  Define extent and branches of pipelineo  Doesn’t have to be Prod straight away!2.  Define triggers and gates for your pipeline phaseso  How many of these can you automate?3.  Do only validated code/artifacts get passeddown the pipeline?o  Watch out if new components are introducedlater on
  24. 24. 5 Steps Towards Continuous Delivery4.  Who needs to know/be able to control what?o  Job settings and deployed configurationsettings can be invisible
  25. 25. 5 Steps Towards Continuous Delivery4.  Who needs to know/be able to control what?o  Job settings and deployed configurationsettings can be invisible5.  How much variation across projects/platforms doyou need to handle?
  26. 26. o  They already do it…Convincing Your Managementand many more…
  27. 27. Convincing Your Managemento  Your competitors are working on it…
  28. 28. o  Application Release Trends 2013 Surveyo  go.xebialabs.com/Survey2013.htmo  Dzone Refcard: “Preparing for Continous Delivery”o  refcardz.dzone.com/refcardz/preparing-continuous-deliveryo  “Introducing Continuous Delivery in the Enterprise”o  go.xebialabs.com/EBCDWhitepaper_Continuous_Delivery.htmlo  Continuous Delivery Automationo  www.xebialabs.com/continuous-deliveryMore Information
  29. 29. Thank You!NEXT STEPSo  More information: www.xebialabs.comGET STARTEDo  Deployit Trial: www.xebialabs.com/trialDeployit: www.xebialabs.com/productsBlog: blog.xebialabs.comTwitter: @xebialabsYouTube: youtube.com/xebialabsSTAY INFORMED

×