Continuous Delivery With Team Foundation Server
13
CONTINUOUS DELIVERY WITH TEAM FOUNDATION SERVER February 24, 2015 DANIEL ȘTEFĂNESCU
-
Upload
daniel-stefanescu -
Category
Software
-
view
257 -
download
0
Transcript of Continuous Delivery With Team Foundation Server
CONTINUOUS DELIVERY
WITH
TEAM FOUNDATION SERVER
February 24, 2015
DANIEL ȘTEFĂNESCU
WHAT'S IN A NAME?
CI, CD and CD
• Continuous IntegrationEvery code change integrates, builds, and tests within the
development environment.
• Continuous DeploymentEvery code change that passes the automated tests is deployed to
production automatically.
• Continuous DeliveryKeeps the deployment decision as a manual step.
TITLE PRESENTATION February 24, 2015
WHAT'S IN A NAME?
Difference between
Continuous Delivery
Continuous Deployment
TITLE PRESENTATION February 24, 2015
Code Done Auto Unit Tests Auto Integrate AutoAcceptance
TestAuto
Deploy To PROD
Continuous Delivery thumb rule:Every checkin should be a release candidate but the release should be a political decision and done manually
Code Done Auto Unit Tests Auto Integrate AutoAcceptance
TestManual
Deploy To PROD
WHY CONTINUOUS DELIVERY?
• What is the cost for your production system to be down due to
a rogue release or change?
• What is the cost of wait-time for Operations to release a new
feature into production?
• What is the cost of not having transparency of which software
version has been deployed to an environment?
• What is the risk factor of manual steps for a release?
TITLE PRESENTATION February 24, 2015
QUICK TEST
Question:
If a stakeholder requests that the current development version
of the software can be deployed into production at a moment's
notice what would be the reaction?
CD enabled answer:
Nobody would bat an eyelid.
Non-CD enabled answer:
Panic mode on.
TITLE PRESENTATION February 24, 2015
CONTINUOUS DELIVERY WITH TFS
Release Management for Visual Studio
The continuous delivery solution that automates the release
process through various environments all the way to production.
Topology• RM Server for TFS
• RM Client for Visual Studio
• Microsoft Deployment Agent
TITLE PRESENTATION February 24, 2015
CONTINUOUS DELIVERY WITH TFS
Release Management Concepts
• Release Template
TITLE PRESENTATION February 24, 2015
Release Template
Release Path
Workflow TFS Build
CONTINUOUS DELIVERY WITH TFS
Release Management Concepts
• Release Path
TITLE PRESENTATION February 24, 2015
Release Path
Stage
EnvironmentApproval Workflow
CONTINUOUS DELIVERY WITH TFS
Release Management Concepts
• Workflow
TITLE PRESENTATION February 24, 2015
Workflow
Component
Release Input
Tools
Actions
Tools
RELEASE MANAGEMENT - LICENSING
• Each person using the Release Management Client for Visual
Studio 2013 for creating, updating, or deleting a release
pipeline sequence must be licensed for either Visual Studio
Ultimate with MSDN, Visual Studio Premium with MSDN,
Visual Studio Test Professional with MSDN, or MSDN
Platforms.
• A user who only approves stages or signs off on a release
does not need to be licensed
• Target servers receiving automated deployment from Release
Management Server no longer require a Visual Studio
Deployment license.
February 24, 2015TITLE PRESENTATION
RELEASE MANAGEMENT
• DEMO
– Setup
February 24, 2015TITLE PRESENTATION
Team Foundation Server
Build Controller/Agent
Release Management
Server
Release Management
Client
DEV
Web
• IIS
• RM Deployment Agent
Database
• MS SQL
• RM Deployment Agent
QA
Web
• IIS
• RM Deployment Agent
Database
• MS SQL
• RM Deployment Agent
Test AgentTest Controller
WRAP-UP
February 24, 2015TITLE PRESENTATION
We’ll Never Get To Space on Horseback
