Upload
microsoft-visual-studio
View
6.043
Download
1
Tags:
Embed Size (px)
Citation preview
Jeff Fattic
Introducing Release Management for Team Foundation Server 2013
Application lifecycle trends
Cloud Services
Business AgilityContinuous
Quality
Multi Platform Multi Device
Continuous Feedback
Heterogeneousdevelopment
teams
Continuous Delivery
SocialUser-Centric
Release management needs & challengesMore frequent releasesHow do we elegantly shift from long release cycles to monthly, or even daily?
Customer responsivenessHow can we help set customer expectations about when bug fixes and feature requests go live?
Stakeholder transparencyHow can we make sure everyone understands the release pipeline so they can do their jobs?
Compliance & regulationHow can we feel confident we’re properly tracking, managing, and approving our releases?
Plan REQUIREMENTS
BACKLOG
RELEASE
OperateConstruct
WORKING SOFTWARE
Develop
OperateAgile portfolio management
Team RoomGitCode Information Indicators
.NET memory Dump Analyzer
Visual Studio and System Center integration
Build | Measure | Learn
Integrated release management
Collaborate
Kanban customizationWork item tagging
Release
Performance events
Continuous value
Load Testing as a Service
Configuration-based deployments
Optimizing the release cycle
DEV QAINT PRODTeam
FoundationServer
Coordination
Testing time
ProvisionDeploy
Release process
Build &PackageCode
DeployDeployDeployDeployDeployDeploy DeployDeploy
Test Prod DeployDeployProvision
Release ManagementA continuous deployment solution for .NET teamsAutomates the deployment processSimplifies managing multiple environmentsImproves collaboration throughout the processProvides release analytics and reporting
HistoryOriginally launched in 2009 as InRelease by InCycle SoftwareInRelease 2.0 launched in 2010, 3.0 in 2013Acquired by Microsoft in 2013
Release Management componentsRelease Management Client for Visual Studio 2013 is available with:Visual Studio Test ProfessionalVisual Studio PremiumVisual Studio Ultimate
Release Management Server for Team Foundation Server 2013Microsoft Deployment Agent 2013Required per deployment nodeLicensed separately
Team Foundation
ServerDrop Location
RM ClientRM Web
QA
DEV
RM Server
How it works
Release paths & configuration demo
Configuration tokensDeployment challenge: environment settingsEach environment (Dev, QA, Production) have their own settings, such as connections strings
Release Management solution: configuration tokensConfiguration tokens provide a way to inject environment settings at deploy-time
How it worksCreate a .token file that mirrors your configuration file, but uses tokens for configurable fieldsFor example, if your Web config has:
You can add a Web.config.token that has:
SummaryMore frequent releasesCustomer responsivenessStakeholder transparencyCompliance & regulation
© 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.