Continuous Delivery in the Enterprise
•
0 likes•314 views
Continuous Delivery is easy in development projects and modern organisation who delivery services but how is it with all the enterprise customers? How do get continuous delivery when we work with "customized COTS"?
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Continuous Delivery in the Enterprise
Similar to Continuous Delivery in the Enterprise (20)
More from Michael Medin
More from Michael Medin (20)
Recently uploaded
Recently uploaded (20)
Continuous Delivery in the Enterprise
- 5. TWO GIRLS
- 7. PINK LEGOs!
- 9. R2M Simply the best Open Source Commercial Java .netIntegration Method
- 10. R2M Automation, CI/CD, DevOps …even with commercial vendors
- 11. R2M We love knowledge! Competence Fall Coding After Work Conferences
- 16. THEORY
- 29. complexity++ DEV WEB/APP DB WEB/APP WEB/APP LB APPESB DEV2 WEB/APP DB WEB/APP WEB/APP LB APPESB TEST WEB/APP DB WEB/APP WEB/APP LB APPESB AT WEB/APP DB WEB/APP WEB/APP LB APPESB ST WEB/APP DB WEB/APP WEB/APP LB APPESB PRE PROD WEB/APP DB WEB/APP WEB/APP LB APPESB PROD WEB/APP DB WEB/APP WEB/APP LB APPESB
- 39. Code Integrate Build Unit-test Deploy Acceptance/ Integration test Release systems not enterprise
- 43. no such thing…
- 47. HOW?
- 50. AUTOMATE Code Test Release Install Configuration Deploy Acceptance Test Migration Everything Regression Test Build
- 52. LIES!
- 53. …but we use product X… people say: …it’s impossible
- 54. LIES!
- 56. Shamelessly stolen from Adrian Cockcroft
- 59. is key DevOps
- 60. AUTOMATE Code Test Release Install Configuration Deploy Acc. Test Migration EverythingBUILD IT we need to
- 61. DevOpsNot about: working together It’s about working together remember
- 63. NOT MONEY FREE
- 65. Accumulated cost 0 20 40 60 80 100 120 140 0 1 2 3 4 5 6 Manual Automated
- 66. Accumulated cost 0 20 40 60 80 100 120 140 1 2 3 4 5 6 7 Manual Automated Re invest in CD
- 67. Project cost 0 50 100 150 200 250 300 350 400 Project A Project B Project C Project D Project E Hours
- 68. Project cost 0 50 100 150 200 250 300 350 400 Project A Project B Project C Project D Project E Hours Investing in CD Still saved money
- 70. Practice Build management and CI Environments and deployment Release management Testing Data management Configuration Management Level 3 – Optimizing: Focus on process improvement Teams regularly meet to discuss integration problems and resolve them with automation, faster feedback, and better visibility All environments managed effectively. Provisioning fully automated. Virtualization used if applicable. Operations and delivery teams regularly collaborate to manage risks and reduce cycle time. Production rollbacks rare. Defects found and fixed immediately. Release to release feedback loop of database performance and deployment process Regular validation that CM policy supports effective collaboration, rapid development, and auditable change management processes. Level 2 – Quantitatively managed: Process measured and controlled Build metrics gathered, made visible, and acted on. Build s are not left broken. Orchestrated deployments managed. Release and rollback processes tested. Environment and application health monitored and proactively managed. Cycle time monitored. Quality metrics and trends tracked. Non functional requirements defined and measured. Database upgrades and rollbacks tested with every deployment. Database performance monitored and optimized. Developers check in to mainlined at least once a day. Branching only used for releases. Level 1 – Consistent Automated processes applied across whole application lifecycle Automated build and test cycle very time a change is committed. Dependencies managed, Re-use of scripts and tools. Fully automated, self- service push-button process for deploying software. Same process to deploy to every environment. Change management and approvals processes defined and enforced. Regulatory and compliance conditions met. Automated unit and acceptance tests, the latter written with testers. Testing part of development process. Database changes performed automatically as part of deployment process. Libraries and dependencies managed. Version control usage policies determined by change management process. Level 0 – Repeatable: Process documented and partly automated Regular automated build and testing. Any build can be re- created from source control using automated process. Automated deployment to some environments. Creation of new environments is cheap. All configuration externalized / versioned Painful and infrequent, but reliable, releases. Limited traceability from requirements to release. Automated tests written as part of story development. Changes to databases done with automated scripts versioned with application. Version control in use for everything required to recreate software: source code, configuration, build and deploy scripts, data migrations. Level -1 – Regressive Processes unrepeatable, poorly controlled, and reactive Manual process for building software. No management of artifacts and reports. Manual process for deploying software. Environment-specific binaries. Environments provisioned manually Infrequent and unreliable releases. Manual testing after development. Data migration unversioned and performed manually. Version control either not used, or check-in happens infrequently. Capability Maturity ModelLevel 1 Consistent Automated processes applied across whole application lifecycle Automated build and test cycle very time a change is committed. Dependencies managed, Re-use of scripts and tools. Fully automated, self-service push-button process for deploying software. Same process to deploy to every environment. Level 0 Repeatable: Process documented and partly automated Regular automated build and testing. Any build can be re-created from source control using automated process. Automated deployment to some environments. Creation of new environments is cheap. All configuration externalized / versioned Level -1 Regressive Processes unrepeatable, poorly controlled, and reactive Manual process for building software. No management of artifacts and reports. Manual process for deploying software. Environment-specific binaries. Environments provisioned manually Level 1 Consistent Automated processes applied across whole application lifecycle Automated build and test cycle very time a change is committed. Dependencies managed, Re-use of scripts and tools. Fully automated, self-service push-button process for deploying software. Same process to deploy to every environment. Level 0 Repeatable: Process documented and partly automated Regular automated build and testing. Any build can be re-created from source control using automated process. Automated deployment to some environments. Creation of new environments is cheap. All configuration externalized / versioned Level -1 Regressive Processes unrepeatable, poorly controlled, and reactive Manual process for building software. No management of artifacts and reports. Manual process for deploying software. Environment-specific binaries. Environments provisioned manually
- 73. Our job is to automate business processes. Why do we do this manually?
- 74. Photo by Olga Berrios