Continuous Delivery at Oracle Database Insights
0 likes563 views
The document discusses continuous delivery and DevOps practices, emphasizing the importance of automation throughout the software development lifecycle. It outlines various maturity levels for processes related to integration, testing, deployment, and change management, providing a framework for optimizing and improving development practices. Key points include the need for collaboration, monitoring, and automation to overcome challenges in delivery and maintain effective software quality.
Continuous Delivery at Oracle Database Insights
- 4. TWO GIRLS
- 6. PINK LEGOs!
- 7. R2M Amazing!
- 8. THEORY
- 20. 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
- 32. no such thing…
- 37. AUTOMATE Code Test Release Install Configuration Deploy Acceptance Test Migration Everything Regression Test Build
- 38. people say: …this is very hard… …it’s impossible
- 39. LIES!
- 40. …we use product X… people say: …it’s impossible
- 41. LIES!
- 42. …we don’t have time… people say: …it’s impossible
- 43. LIES!
- 47. AUTOMATE Code Test Release Install Configuration Deploy Acc. Test Migration EverythingBUILD IT we need to
- 49. DevOps
- 50. DevOpsNot about working together It’s about working together remember
- 51. Javasource • Edit • Compile build • Test • Package package • Archive • Version runtime • Deploy • Manage
- 52. Database • Edit • Compile Agresso
- 53. Agresso Database • Edit • Compile Change management Reverting Your not alone!
- 56. Deploy: Time per week: Consultants: 1 per week 3-4 20h Every week!
- 57. Accumulated cost 0 20 40 60 80 100 120 140 0 1 2 3 4 5 6 Manual Automated
- 58. Accumulated cost 0 20 40 60 80 100 120 140 1 2 3 4 5 6 7 Manual Automated Re invest in CD
- 60. 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
- 62. Our job is to automate business processes. Why do we do this manually?
- 63. Photo by Olga Berrios