Top Banner
Continuous delivery with Release Management for Visual Studio Marcel de Vries @marcelv http://nl.linkedin.com/in /marcelv
24

Continuous delivery with Release Management for visual Studio

Dec 01, 2014

Download

Technology

Marcel Vries

Session presented for DotNed 20 feb 2014
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Continuous delivery with Release Management for visual Studio

Continuous delivery with Release Management for Visual StudioMarcel de Vries @marcelvhttp://nl.linkedin.com/in/marcelv

Page 2: Continuous delivery with Release Management for visual Studio

Daily forces and the road to continuous XDevelopment teams work using agile methodologies

Page 3: Continuous delivery with Release Management for visual Studio

Daily forces and the road to continuous XIT Departments most of the time split in at least two entities

Page 4: Continuous delivery with Release Management for visual Studio

Daily forces and the road to continuous XWell established boundaries

Page 5: Continuous delivery with Release Management for visual Studio

Optimized processes

Deliver MVP’s so we can learn what customer really needs

Keep machines and infra as stable as possible

Page 6: Continuous delivery with Release Management for visual Studio

PRODUCT BACKLOG

OPS BACKLOG

Sprint Monitor

Define

Deliver

Operate

Sprint

Define

DeliverCUSTOMERSComplexError-proneChaotic

Learn

Deploy

Page 7: Continuous delivery with Release Management for visual Studio

Continuous deployment

ContinuousBuild

ContinuousTest

ContinuousDeploy

Continuous Learning

Page 8: Continuous delivery with Release Management for visual Studio

Release Process

Build &PackageCode

DeployDeployDeployDeployDeployDeploy DeployDeploy

Test Prod DeployDeployProvision

Page 9: Continuous delivery with Release Management for visual Studio

Automate The Release Cycle

DEV

Automates Deployments

TEST QA PRODCode

Automate the Release Cycle

Page 10: Continuous delivery with Release Management for visual Studio

FS

Deploys the same way to all stages

DEV TEST QA PRODCode

Automate the Release Cycle

Page 11: Continuous delivery with Release Management for visual Studio

Automate The Release Cycle

Automates Workflow

DEV TEST QA PRODCode

Automate the Release Cycle

Page 12: Continuous delivery with Release Management for visual Studio

Automate The Release Cycle

Full Traceability

DEV TEST QA PRODCode

Automate the Release Cycle

Page 13: Continuous delivery with Release Management for visual Studio

What can TFS bring to the table?

Full traceable way of building the deployment package

Full traceable way of deploying the software

Management environment

Page 14: Continuous delivery with Release Management for visual Studio

TFS Drop Location

IR DesktopIR Web

QA

DEV

IR Server

How it Works

CUSTOMERS

Page 15: Continuous delivery with Release Management for visual Studio

Automated Tests

Stage Stack

InstallApplication

ProvisionEnvironment

Create Test Data

ConfigureEnvironment

ConfigureApplication

Manual Tests

Notify Approvers

Approve Stage

Appro

val

Test

sA

pp

Infr

a

MTM

Lab Manager

MS Tools / TfsDeployer

InRel

ease

Page 16: Continuous delivery with Release Management for visual Studio

TFS Release management conceptsRelease A defined set of software components that can be related back to requirements and sourcesIs tracked in TFS from start to endIs fully traceable trough all stages

Deployment pathA set of stages software needs to be deployed on it’s path to production

DEV TEST QA PROD

Page 17: Continuous delivery with Release Management for visual Studio

TFS Release management conceptsEnvironmentSet of machines where we deploy our software

Tool / ActionA tool is software required to carry out a deployment taskAn Action is a preconfigured way of using the tool for deployment purposes

Component Part of the software that we want to deploy and is one self contained entityHas a Source (e.g a build drop)Has a deployment definition (using a tool)Has configuration variablesIs used in a release template

Page 18: Continuous delivery with Release Management for visual Studio

TFS Release management conceptsRelease templateDefines how to deploy a component to an environment

Machine in the environment where we

deployDeployment action

Component deployment

Page 19: Continuous delivery with Release Management for visual Studio

Demo

Page 20: Continuous delivery with Release Management for visual Studio

Designed to work cross network boundaries

Deploy agents work based on a pull modelNo additional ports open on the target machineAgents pull their own updates, to keep tools up to date

Tools for deployment also pulled to serverYou place your tools in the tool and the deploy agent downloads the toolsNo need for install on server, it is slipstreamed on the server

Proxy for dop locationTFS drop location normally not available on production serverIn release server can act as proxy for the deployment drop

Page 21: Continuous delivery with Release Management for visual Studio

TFS release management

Enable an optimized process cross organizational boundaries

Page 22: Continuous delivery with Release Management for visual Studio

Where to start

Start the learning loop

Page 23: Continuous delivery with Release Management for visual Studio

Where to start

Optimize based on your learning

Lean can help

Page 24: Continuous delivery with Release Management for visual Studio

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.