ms-release-management

问题 I'd like to be able to setup a WinRM dacpac deployment task in MS Release Management to create a report of the schema compare and not actually deploy the database. Then I could have an environment approval and abandon the deployment if unexpected changes are reported. If the changes are as expected, the next environment would actually deploy the database. Is there a way to do that using the available WinRM DB deployment task? If so, how? 回答1: 'Publish' is hardcoded in the task script, so we

问题 A Build definition has a custom variable that can be set when a build is queued. Is possible to have access to that variable from a Release in the same way that is possible to have access to variables like Build.DefinitionId, Build.DefinitionName, Build.BuildNumber ? 回答1: A custom build variable couldn't be used in your release definition. Here is an user voice that similar to your problem: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/14515326-project-level-build

问题 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

问题 I'm using TFS 2015.2 RTM and I just found out that the Release Management vNext REST API is in 2.2-preview.1 on-premises. I want to create a release, but I don't know the exact JSON to put in the body of the POST request since the documentation only works for VSTS. When I send the request, I get the error message: VS402881: No artifact version is specified corresponding to artifact source 'MyBuild.' Specify a valid value and try again. Here's the JSON: $body = @" { definitionId": 1,

问题 I'm using TFS 2015.2 RTM and I just found out that the Release Management vNext REST API is in 2.2-preview.1 on-premises. I want to create a release, but I don't know the exact JSON to put in the body of the POST request since the documentation only works for VSTS. When I send the request, I get the error message: VS402881: No artifact version is specified corresponding to artifact source 'MyBuild.' Specify a valid value and try again. Here's the JSON: $body = @" { definitionId": 1,

问题 In TFS 2017 Update 1 after downloading programmatically a release definition with REST api, I edited the downloaded json and uploaded again programmatically. The changes are present. However the server phase of manual intervention is missing in the environments after the changes. Can someone else reproduce it? The program C# to download and upload the release definition is at my github page githubpage 回答1: Use api-version=3.2-preview.3 instead of 3.0-preview.2 when you update the release

问题 Using agent-based release templates, not vNext, how do I configure a "Create Folder" item so that it incorporates the date into the folder name, e.g. "C:\inetpub\wwwroot\backups\MyApp\02-03-2015\". Preferably, I would like the build number instead of the date but I believe it's only available to vNext templates. -edit- unless you're using components I'm trying to implement some backup and rollback logic as part of the my release pipeline. I want to copy the existing web code to a backup

问题 Using agent-based release templates, not vNext, how do I configure a "Create Folder" item so that it incorporates the date into the folder name, e.g. "C:\inetpub\wwwroot\backups\MyApp\02-03-2015\". Preferably, I would like the build number instead of the date but I believe it's only available to vNext templates. -edit- unless you're using components I'm trying to implement some backup and rollback logic as part of the my release pipeline. I want to copy the existing web code to a backup

问题 In TFS 2017 Update 1 (On-Prem) there is a release definition with a manual intervention step in between. The manual intervention notification is set for a group where an user User1 is not part of. User1 has Builder and Project Admin rights; And is also part of the TFS team. During the manual intervention of a release User1 is able to resume or reject the release. But we don't want this to happen. I could not find the rights in TFS Microsoft online documentation for being able to do this. What

问题 I'm trying to connect a Deployment Agent to my Release Management server with TFS (all running Update 2). The Release Management server is outside the network of the test environment servers. It can be reached over HTTP. The test environment is running behind a proxy. I've changed the configuration of the config files to make sure connecting through the proxy works by adding this: <system.net> <defaultProxy enabled="true" useDefaultCredentials="true"> <proxy usesystemdefault="True"