This is an introductory course designed to help you get up and running with Release Management. We'll start with basic installation and setup, then move on to configuration of the different building blocks that make Release Management tick. Then we'll walk through examples of deploying an ASP.NET web application, a Windows Service application, and a SQL Server database. These examples will include methods of manual deployment, as well as automated deployment. By the end of the course, you will be able to use Release Management for Microsoft Visual Studio 2013 to enable consistent, rapid, and automated deployments in your own work environments.
David is a software developer with a back ground in IT systems administration. When he’s not learning something new about technology, or speaking about technology, he enjoys billiards and watching/attending motocross races.
Introducing Release Management Hello, and welcome to Pluralsight's course "Getting Started With Release Management for Visual Studio 2013. " My name is David Batten and we're going to talk about and explore Microsoft's newest tool for the ALM stack. Release Management fills a gap in a rich set of tools for delivering software to our customers. For some time, Microsoft has given us the majority of the building blocks we need as IT professionals, things like Visual Studio, Windows Server, SQL Server, and Team Foundation Server, but they have lacked a comprehensive software delivery tool that can help organizations focus on continuous delivery and rapid deployments. Release Management fills that void and provides excellent integration with the existing tools in the Microsoft ALM stack. To be successful with this course, you'll want to start with the following environment. The version of Team Foundation Server that I have installed is 2013. I also have Visual Studio 2013 for use with the demo projects that we will be deploying. All database deployments will be targeted at SQL Server 2008 R2. And, all applications deployments will be targeted at Windows Server 2008 R2. All examples in this course were created using Update 2 of Release Management. So, be aware that if you're on an older version, you may see some different view elements than you see in the course. And, if you're on a newer version, you may also have some additional features that aren't covered in this course.
Release Paths Welcome to Pluralsight. In this module, you will be introduced to release paths, which play a very important role in Release Management. Release paths contain three major parts: Servers, environments, and the release path definitions. They define which environments a software release can target, including the order in which those environments are targeted. Release paths have an approval system that allows us to control what groups and/or individuals can move releases into which environments. It can be completely automated, completely manual or anywhere in between. This approval system also includes the ability to send notifications to interested parties as your apps move through the release pipeline. All of this provides for a robust deployment environment that can be as controlled as you need it to be to satisfy the security and auditing requirements of your business. We'll start by registering our servers with the Release Management client.
Release Management in Action Welcome to Pluralsight. This is David Batten and in this module, we're going to create our first release template and spawn a release from it. This is our opportunity to leverage all the configuration and building blocks we've created thus far as we deploy some applications to our target servers. We'll begin with a template and release for a web application, then continue on with the release of a Windows service application, and finally, we'll deploy a database project to an instance of SQL Server. This should give you a great foundation for creating releases for anything your team needs to deploy.