Continuous delivery chernivcy
Upcoming SlideShare
Loading in...5
×
 

Continuous delivery chernivcy

on

  • 382 views

How Continuous delivery may help develop more officient delivery process

How Continuous delivery may help develop more officient delivery process

Statistics

Views

Total Views
382
Views on SlideShare
273
Embed Views
109

Actions

Likes
0
Downloads
1
Comments
0

11 Embeds 109

http://anclevovan.blogspot.com 84
http://anclevovan.blogspot.ru 7
https://www.commafeed.com 6
http://commafeed-megapoliss.rhcloud.com 3
http://anclevovan.blogspot.co.uk 2
http://anclevovan.blogspot.de 2
http://newsblur.com 1
http://www.yatedo.com 1
http://anclevovan.blogspot.kr 1
http://anclevovan.blogspot.fr 1
http://anclevovan.blogspot.sg 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Continuous delivery chernivcy Continuous delivery chernivcy Presentation Transcript

  • Continuous DeliveryOne click delivery at any time
  • 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
  • General process Build Deployment Acceptance Release Production
  • Parallel Development Strategies▪ Release Branch▪ Maintenance Branch▪ Feature Branch▪ Team Branch Parallel Development Strategy
  • 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
  • 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
  • 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
  • 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
  • Repository Management ToolFeatures▪ Repositories management▪ Permission management▪ Simple code review
  • 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
  • Deployment Unified deployment process to all environments QC RC Environment Artifact Artifact Configuration Preparation Deployment Repository FATStaging Production Performance Build Deployment Acceptance Release Production
  • 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
  • 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
  • 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
  • Release RC Release Artifact Artifact Repository RepositoryBuild Deployment Acceptance Release Production
  • Production▪ One click at any time Build Deployment Acceptance Release Production
  • Questions