ms-release-management

We just started using Visual Studio Release Management for one of our projects, and we're already having some problems with how we are doing things. For now, we've created a single release stage, which is responsible for deploying our build artifacts to a dedicated virtual machine for testing. We intend to use this machine to run our integration tests later on. Right now, we have a gated checkin build process: each checkin fires all the unit tests and we configured the release trigger to happen on this build also. At first, it seemed plausible that, after each checkin, the project was deployed

I am new to Visual Studio Team Services Release Management. My goal is to automate a deployment of an ASP.NET MVC application to the Azure App Service. Trying different approaches, I created a Service Endpoint that is certificate based and one that uses a service principal (SPN). My build definition already builds a web deploy package, and the release definition is linked against that and can use this artifact. Success 1: A deployment of the app using the Azure Web App Deployment Task already succeeded - almost. Shortcoming 1: I do not understand how I can specify the correct Resource Group

We are using Microsoft's Release Management tool for automating the deployment of our solution to our various dev servers. This tool is ideal for us because it can perform more complicated deployments that span multiple servers. In this sense, it is working fine and everything is deploying correctly. A minor issue is that after Release Management automatically deploys a build, it sets the build to "Retain Indefinitely" which is indicated by the Lock icon. Since we are doing continuous deployment, we are retaining a large number of builds and the Build Definition's retention policy is

Background Information TFS 2015 RC2 Release Management Server 2015 Azure VM with 2015 deployment agent Physical local machine with 2015 deployment agent Both machines need the drop location using the Through Release Management Server over HTTP(S) option. Currently we are using the HTTP side of things over port 1000. Workflow Stop App Pool (Working) Stop Website (Working) Copy website directory to backup location (Working) Backup Database (Working) Deploy Component (Not Working), using either xcopy msdeploy (web deploy package) The Error (TL;DR) The same error is received every time, it doesn't

I am using VSTS build to run a CI build. This build definition is the same for all my git branches (master, develop, features, etc). I am now trying to implement a deployment pipeline using VSTS release management. I plan to have two distinct release definitions. One for feature branches and one for the more important branches like develop and master. The release definition for feature branches would be more lightweight. I think this is pretty basic and usual. In fact, that's pretty much what is documented in Microsoft's typical use case for Release Management . For both of these pipelines, I

I am setting our build/release environment using TFS 2017. I set up the Build to run automatically after each commit, and when we are ready to release a version of our application, a Release is manually created, and then deployed to various environments. We would like to tag released versions in our git repository in order to easily know which git revision correspond to a binary. The "Label Source" setting in the Build definition allows to tag a git revision at build time, but since we build on every commit that would generate a lot of tags which we don't care about (as they are not deployed

I'm trying to implement continuous integration and continuous deployment to my DEV Azure App Service. I'm using the hosted agent on Visual Studio Team Services. The "Deploy Website to Azure" step on my Release definition keeps failing with the error "No package found with specified pattern". Any ideas? Eddie Chen - MSFT "More than one package matched with specified pattern. Please restrain the search patern [sic]." error usually occurs when 2 or more packages were found by the task since you entered "xxx\*.zip" in "Package or Folder" setting of the task. So you just need to update it to

How can I rename a file in a release definition in Visual Studio Team services? Is there a built-in or marketplace task available or otherwise, how can this be achieved? Answer: Add the "Inline PowerShell" task from the marketplace Enter the following PowerShell code in the text area Param ( [string]$pathToFileToRename ) Rename-Item $pathToFileToRename NewName.txt Enter any required arguments in the arguments text box (you can use environment variables), for example. pathToFileToRename $(System.DefaultWorkingDirectory)/somepath/CurrentName.txt Use the Run Command Line task or do it in a