This document provides an overview of implementing DevOps for the Microsoft platform. It discusses DevOps practices like continuous integration, continuous deployment, and release management using tools like Team Foundation Server. The agenda includes discussing DevOps concepts, why organizations adopt DevOps, and how to establish an automated CI/CD pipeline for code, databases, and releases.

1. Implementing DevOps for Microsoft Platform
Presented By: Ranbir Dhial & Umesh kumar

2.  What is DevOps
 Why DevOps
 DevOps Implementation
 DevOps Practices
 Continuous Integration and deployment using TFS
 Website and DB changes
 Code and Build
 Setting up Release Management Agent
 Configuring Release Management Workflow
 Establishing Release Management Pipeline
 Dashboards and Reporting
Agenda:

3. DevOps Overview

4. Today’s business and technical needs are pushing traditional delivery approaches to the breaking
point
Delivery Challenges

5. Definitions
Applying agile techniques to operations
Getting development and operations to work
together
DevOps is the last mile of Agile
How to deploy software with speed and
confidence
DevOps is about accelerating software
deployment
Characteristics
Treating “Infrastructure as Code” is fundamental
to DevOps
Automating the work of setting up and
maintaining systems infrastructure
Making it defined, efficient, testable, auditable
and standardized
Automated Testing is part of your pipeline
Automated CI / CD pipeline
Automated application deployment
Logging & Traceability of all changes
What is DevOps

6. From Agile to DevOps

7. Do we really need DevOps?
Developers always want to deliver changes as soon as
possible.
Operations want reliability and stability.

9. Ops / ITIL Values:
•Procedure Driven
•Stability
•Availability/Uptime
•Controlled/Frozen environment
•Infrequent Updates
Results in:
Long Lead Time
Limiting the # of Changes
Infrequent Deployments
Agile Dev Values:
•Business Driven
•Responsive to Change
•Real Time
•Constantly up to date
environment
•CI / CD Environment
Results in:
Short Sprints (2-3 wk)
Lots of small changes
Frequent Deployments
Ops vs Dev

10. 7Cs OF DevOps
1. Communication
2. Collaboration
3. Controlled Process
4. Continuous Integration
5. Continuous Deployment
6. Continuous Testing
7. Continuous Monitoring
Agile mantra “People over
Process over Tools”. With the right people, we establish the
right process and choose the right tools to deliver the end
Results
• People – Communication & Collaboration
• Process – Source Control Check-ins, Code Review, Code
Quality, Change Control, RCAs
• Tools – For Continuous Delivery (achieve by the
combination
of Continuous Integration, Continuous Deployment and
Continuous Testing) and Continuous Monitoring

11. One Team, One Goal

14. Hard To Achieve DevOps without automation
 Automate Provisioning - Infrastructure as Code
 Automate Builds – Continuous Integration
 Automate Deployments – Defined Deployment Pipeline and Continuous
Deployments with appropriate configurations for the environments
 Automate Testing – Continuous Testing, Automated tests after each
deployment
 Automate Monitoring – Proper monitors in place sending alerts
 Automate Metrics – Performance Metrics, Logs

15. DevOps Practices

16. DevOps Practices
1. Branching strategy
2. Continuous Integration using TFS
1. Code
2. Database
3. Test Automation
4. Continuous Deployment / Release Management
5. Setting up Release Management Agent
6. Configuring Release Management Workflow
7. Establishing Release Management Pipeline

17. 7/13/201717
CI to Trunk Enables Release On Demand
Epic/Feature Branch A
Trunk
Release 1
Epic/Feature Branch B
Epic/Feature Branch C
Check-Ins
Check-Ins
CI Builds &
Test Runs
Trunk Merges
Release Label
CI Builds &
Test Runs
Release Label
Reverse
Integration
Forward
Integration
With selective merging, integration to trunk can continue without
dependency to release timing considerations.
Check-in LabelCI Build
Check-Ins
Selective
Merge
Release Hardening Fix Check-In
Release Label

18. 7/13/201718
Release Branch – Rollback Handling
Trunk
Release 1
Release Label
Reverse
Integration
Selective Merge needs Rollback
Check-in Label
Selective
Merge
Release Hardening Fix Check-In
Release Label
Rolled Back
Check-in

19. Process Activities and Timelines
Activity Branch Performed By Proposed Time Line Validation
Check In Feature Developers Anytime Build should not break
Merge Trunk
Leads/Designated People
Often!
At minimum, upon story
QA,BA and PO signed off
Trunk Build should not break (Db and
Website)
Forward Integration Feature Developers
Often! At minimum, at
Sprint Start (Monday India
Day)
Build should not break
Release Branch Trunk
RM with Dev Team Leads
Leads
Per Release Calendar
Confirm Required Change sets are
available per Team wise and Build
successful
Post Release Release Developers ASAP
The intended Release fix validated on a
a lower branch
Reverse Integration Trunk
Leads/Designated People
After Hotfix is validated Trunk Build should not break

20. Continuous Integration
- First step in DevOps Journey
- Provides immediate feedback for the team
- Provides immediate feedback on code quality
when underlying process are automated

21. CI for Databases

22. Database Deployment
- Why DB deployment is different from Code
- Challenges with DB Deployment
- Principles of DB deployment
- What are our options
- How you can get started

23. CI and CD

24. Why Continuous Delivery?
Get faster time to market and respond with greater agility to customer feedback. Design and automate release pipelines across your environments to any target
platform.
Ship with confidence:
Raise the quality bar with every release: Configure tasks for all of your release checkpoints – performance, A/B, functional, security, beta testing and
more. No more release day nightmares.
Orchestrate deployments across targets:
Get control of your deployments:
Manual or automated gates for approval workflows: Enable sign-off for deployments using pre or post deployment approvals. Automatic
notifications ensure collaboration and release visibility among team
End-to-end traceability
Track the status of releases and deployments including commits and work items in each environment.

25. Release Workflow