Orchestrating the Continuous Delivery Process

Transcription

1 Orchestrating the Continuous Delivery SVP Products, CloudBees 1

2 Continuous Delivery Overview Feedback Loop App Lifecycle BUILD TEST STAGE Deploy Run Process Sub-Processes Managed by SMB Continuous Integration Continuous Delivery Development Teams Deployment Enterprise Development Teams Release / Ops Teams DevOps 2

3 Continuous Delivery Defined For the business person: Continuous delivery is a methodology that allows you to deliver new software and update existing software faster, with lower risk For the technical person: Continuous delivery encompasses the set of activities you use to ensure you are ready to deploy code and configuration changes into production at all times In relation to Continuous Integration: CD extends CI to include the concept of deployment and testing for production readiness 3 3

4 4

5 How much? Everywhere? Let s see 5

6 HP LaserJet FutureSmart Firmware - Development costs growing 2.5x from M lines of code - Up to 10 different branches (driven by each product release) % of resources just porting existing FW to new products - Unable to add new products to the plans due to lack of FW resources - 6 weeks + to get through a complete testing cycle (mainly manual) - Ongoing customer issues with consistency and lack of features - Marketing had essentially given up asking for FW innovations 6

7 HP LaserJet FutureSmart Firmware Code Integration 10% Detailed Planning 20% Porting Code 25% Current Product Support 25% Manual Testing 15% Capacity for Innovation ~5% From 2008 to 2011 Continuous Integration 2% Agile Planning 5% One Main Branch 15% One Branch CPE 10% Most Testing Automated 5% Capacity for Innovation ~40% Mike Young, HP, 2011, 7

8 Automation Everywhere! Mike Young, HP, 2011, 8

9 Continuous Delivery Toolchain 9

10 Dev Continuous Integration Starts in Development Code Config Tests Data Build System Build Packager Packages Artifacts & Underlying Systems Source Repo CI Server Artifact Repo Toolchain Push code change Kick off build, tests, more tests Archive artifacts (library,.war file) 10 10

11 Dev Continuous Delivery Emerges for Testing Code Config Tests Data Build System Build Packager Packages Provisioning System Stage Config Automation Source Repo CI Server Artifact Repo Ops Console Resource Model Infra Manager Deploy artifacts to staging area Connect to needed systems/services Run functional and system tests 11 11

12 Ops Has Different Needs Than Dev Dev Code Config Tests Build Build System Stage Packager Packages Provisioning System Config Automation Artifact Repo Ops Console Resource Model Data Source Repo CI Server Build Deploy Ops Environment Specification Tests Infra Manager Packages Build System Provisioning System Packager Treating Configuration as Code Config Automation Images 12 12

13 But the Toolchains Intersect for Dev and Ops Stage Dev Build CI Server Artifact Repo Ops Console Resource Model Infra Manager Ops Source Repo Build Deploy Inspired by:

14 Why the Difference in Toolchain Choices? Dev Speed, coding, functionality, quality Favor local optimization on process, pet tools, fast feedback Ops Auditing, security, compliance, availability, risk avoidance Favor central control, reproducibility, traceability, process Much larger set of constraints, rules, surrounding systems Legacy issues Jenkins is common ground 14 14

15 Continuous Integration Source Code Unit Tests Quality Analysis Binaries 15

16 Continuous Delivery Continuous Delivery Process Source Code DEV Unit Tests Quality Analysis Binaries QA Perfs Environment Func Test Environment UAT Environment DEV Release! Staging Environment OPS Production Environment GO LIVE! 16

17 Tool Tool Tool Tool Tool Tool Tool Tool Tool Tool Tool Jenkins Orchestrates the Toolchain Continuous Delivery with Jenkins BUILD STAGE TEST DEPLOY RUN 17

18 CloudBees Continuous Delivery Platform 18

19 CloudBees Continuous Delivery Platform CloudBees Network Management Monitoring OPERATIONS Operations AT SCALE Provisioning Upgrade Continuous Delivery SOLUTIONS DevOps Mobile Jenkins Operations Center (JOC) CORE JE JE JE JE Hybrid Infrastructure Support HYBRID INFRASTRUCTURE SUPPORT RAW VMW Pivotal 19

20 Flexible, Manageable & Scale JOC Hybrid deployments, abstraction layer JE JE JE JE JE JE JE JE JE JE Static Cloud Linux deployments Deployments IaaS benefit from elasticity/ondemand cloud attributes Customer Private Data Center Pivotal AWS Customer AWS VPC CloudBees Managed Masters and Elastic Slaves CloudBees AWS Account 20

21 Public Cloud BUILD TEST STAGE DEPLOY RUN Build Commit Test Stage Deploy Code CloudBees Continuous Delivery Platform BUILD TEST STAGE DEPLOY RUN On-Premise/Private Cloud 21

22 Improving Continuous Delivery Workflow Many Build Jobs Issues Requires many plugins Workflow definition distributed across many jobs Failures cause big problems! Limited re-usability Build Pipeline View Ref:

23 Jenkins Workflow Adding More Value for CD With Jenkins Workflow New job type Single place for definition Retry-able and restartable Reusable workflows Text-based DSL Build Pipeline View GA Nov One Workflow Job New visualizations coming! 23 23

24 Conclusions The Dev and Ops automation toolchains to support continuous delivery are different, but intersect at Jenkins CloudBees offers a continuous delivery platform based on Jenkins that runs on-prem, in the cloud, or bridges those worlds simply and securely New features being surfaced in Jenkins are extending its reach even further to support continuous delivery 24 24