1. Release Management for Visual Studio 2013 Ana Roje Ivančić Ognjen Bajić Ekobit

2. Inspirirani ljudima. Ugasite mobitele. Hvala.

3. Agenda Release Management Challenges Automating the Release Cycle End-To-End Demo

4. Inspirirani ljudima. Release Management Challenges

5. Release Cycle    

6. Repeatable Automated Deployment Model

7. Deploy high quality low defect SW Release software only when it passes all quality gates Continuously provide value Release Management Goals Lower release costs Achieve more predictable cycles and better task scheduling Clarify the release pipeline so that everyone understands his role Enhance collaboration between Dev, Ops and Stakeholders More frequent releases Shift from long release cycles to monthly, or even daily releases Meet customer expectations about bug fixes and feature requests going live

8. Inspirirani ljudima. Automating the Release Cycle

9. Release Management for Visual Studio 2013 A continuous deployment solution Integrates with TFS ALM Automates the deployment process Simplifies managing multiple environments Improves collaboration throughout the process Provides release analytics and reporting History DevOps begins in 2009 – faster and continuous release cycles Partner Solution - InRelease by InCycle Software Originally launched in 2009, 2.0 in 2010, 3.0 in 2013 Acquired by Microsoft in 2013

10. RM ClientRM Web Environment nEnvironment 1 DA RM Server Release Management Components … ….bat.cmd.ps1.exe

11. Team Foundation Server Drop Location Environment nEnvironment 1 DA RM Server How it Works (1/2) … ….bat.cmd.ps1.exe

12. How it Works (2/2)

13. 3. Inventory Add Tools used for deployment (optional) Create custom Actions (optional) 1. Basic SMTP TFS connection (optional) Users and Groups Stage Types Technology Types (optional) Initially Set Up Release Process in RM Client 4. Application and Releases Create Components for different parts of your application Configure a Release Template to define your deployment process Spawn a Release to execute your deployment 2. Paths Add Servers representing physical target machines Add Environments to group servers Configure a Release Path to set the route to production

14. 14 1. Basic Configuration (1/2) SMTP Set connection to local SMTP in order for RM to send email notifications TFS connection (optional) Integrate with one or more TFS servers Users and Groups Configure users accessing RM server  Release Manager/Service Users TFS/AD groups; RM groups

15. 1. Basic Configuration (2/2) Stage Types Types of stages the deployment must go through (metadata information) Examples: Dev, QA, UAT, PreProd, Prod Technology Types (optional) Metadata used for labeling Environments and Servers with supported technologies

16. 16 2. Paths (1/2): Servers and Environments Add Servers representing target machines Servers must have RM Deployer (aka Deployment Agent) installed  Add Servers manually or scan for Servers Mark Servers with Technology Types Add Environments to group servers Environments consist of one or more Servers Mark Environments with Technology Types

17. 2. Paths (2/2): Release Paths Configure a Release Path to set the route to production Full path for distributing the release to production Map Stage Types to Environments Configure approvers/owners and approval automation for: 1. Acceptance Step 2. Deployment Step 3. Validation Step 4. Approval Step Use different Release Paths for different scenarios: “Standard Development” “Customer Emergency“

18. 3. Inventory: Tools and Actions Add Tools used for deployment (optional) Create custom Actions (optional)

19. 4. Application and Releases (1/4): Components Create Components for different parts of your application 1. Specify how Component gets files used during deployment 2. Configure Tool used to install Component on the target server

20. 4. Application and Releases (2/4): Release Template Configure a Release Template to define your deployment process Select Release Path Select TFS Build Manage security

21. 4. Application and Releases (3/4): Release Template Define Deployment Sequence for orchestrating the deployment in each Stage  Control Flow  Servers  Components  Actions  Tools Copy/paste sequences or elements between Stages

22. 4. Application and Releases (4/4): Release Spawn a Release to execute your deploymen t

24. Automates deployments Automation available to all stages Automates workflow Enables full traceability Automating the Release Cycle DEV QA INT PROD Team Foundation Server

25. Inspirirani ljudima. Pitanja i odgovori. www.ekobit.com aroje@ekobit.com obajic@ekobit.com