Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Continuous DeliveryOne click delivery at any time
Business Challenges▪ Unable Deliver Software In Time▪ Double effort▪ Cross team impact▪ Not all aspects are verified▪ Abil...
General process Build   Deployment   Acceptance   Release   Production
Parallel Development Strategies▪ Release Branch▪ Maintenance Branch▪ Feature Branch▪ Team Branch         Parallel Developm...
Release Branch▪ Pros  – Minimum Overhead  – Easy Release Maintenance (Boxed Products)▪ Cons  – Difficult keep stability wh...
Feature Development▪ Pros  – No Impact to Feature teams until merge  – Ability postpone feature  – Ability release not all...
Hybrid (Proposed Solution)▪ Pros  – Almost Stable “Main”  – Easy Maintenance (SaaS)  – No team impact (isolated)  – More t...
Feature Development Workflow                                                                        Feature A RepositoryRe...
Repository Management ToolFeatures▪ Repositories management▪ Permission management▪ Simple code review
Build                                                 Source                            Dev Team Check-in    Control      ...
Deployment              Unified deployment process to all environments QC                                                 ...
Deployment Steps                       1.   Build                    1.     Application (war)             Installation    ...
Acceptance▪ Smoke Function Automation Tests – Main user workflow based – Component Based▪ Regression Functional Automation...
Acceptance 2▪ Test Production DB Upgrade – Ensure no data related issues – Ensure that maintenance window is matched▪ Test...
Release     RC                                             Release   Artifact                                         Arti...
Production▪ One click at any time Build   Deployment   Acceptance   Release   Production
Questions
Upcoming SlideShare
Loading in …5
×

Continuous delivery chernivcy

713 views

Published on

How Continuous delivery may help develop more officient delivery process

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Continuous delivery chernivcy

  1. 1. Continuous DeliveryOne click delivery at any time
  2. 2. Business Challenges▪ Unable Deliver Software In Time▪ Double effort▪ Cross team impact▪ Not all aspects are verified▪ Ability to deploy any time▪ Global versioning policy
  3. 3. General process Build Deployment Acceptance Release Production
  4. 4. Parallel Development Strategies▪ Release Branch▪ Maintenance Branch▪ Feature Branch▪ Team Branch Parallel Development Strategy
  5. 5. Release Branch▪ Pros – Minimum Overhead – Easy Release Maintenance (Boxed Products)▪ Cons – Difficult keep stability when dev team is big – Developers works on several branches at the same time Parallel Development Strategy
  6. 6. Feature Development▪ Pros – No Impact to Feature teams until merge – Ability postpone feature – Ability release not all features▪ Cons – Higher overhead for merging – Merging issues on latest stages
  7. 7. Hybrid (Proposed Solution)▪ Pros – Almost Stable “Main” – Easy Maintenance (SaaS) – No team impact (isolated) – More team responsibility▪ Cons – Additional overhead for merging Parallel Development Strategy
  8. 8. Feature Development Workflow Feature A RepositoryRepo isCreated Developer Code Push Code Review Code Integration Feature Repo is Deleted Developer Code Push Development Repository Feature X Repository
  9. 9. Repository Management ToolFeatures▪ Repositories management▪ Permission management▪ Simple code review
  10. 10. Build Source Dev Team Check-in Control System F a i Build Job l RC Yes Artifact Promote / Status TC Unit Tests Repository No Code Quality Build Deployment Acceptance Release Production
  11. 11. Deployment Unified deployment process to all environments QC RC Environment Artifact Artifact Configuration Preparation Deployment Repository FATStaging Production Performance Build Deployment Acceptance Release Production
  12. 12. Deployment Steps 1. Build 1. Application (war) Installation 2. Unit & smoke test 2. Migration scripts 1. DB Update 3. Increment version 2. App deployment 4. Package ISV Vendor Sources Artifacts Artifacts Repository Build QCSource Control Repository Offshore Vendor Installation 1. DB Update 2. App deployment QC Build Deployment Acceptance Release Production
  13. 13. Acceptance▪ Smoke Function Automation Tests – Main user workflow based – Component Based▪ Regression Functional Automation Tests – According to Impact▪ Full Regression Functional Automation Tests – For critical release▪ Manual Acceptance Testing – By product owners Build Deployment Acceptance Release Production
  14. 14. Acceptance 2▪ Test Production DB Upgrade – Ensure no data related issues – Ensure that maintenance window is matched▪ Test provisioning/unprovisioning procedure – Ensure that setup of new client is not impacted▪ Performance Testing▪ Operation Testing (DevOps) – Ensure system is monitored and controlled Build Deployment Acceptance Release Production
  15. 15. Release RC Release Artifact Artifact Repository RepositoryBuild Deployment Acceptance Release Production
  16. 16. Production▪ One click at any time Build Deployment Acceptance Release Production
  17. 17. Questions

×