azure-pipelines-release-pipeline

问题 Whats the proper way to form relative file path/ or file path for the runsettings parameter <SettingsFile>xxxxxAutomation.testsettings</SettingsFile> In my local environment this works but when i push it to build release agents it fails since its looking for the file in a different directory which is my release folder but instead its looking for this file in what appears to be in a folder directory. This is the directory its looking at E:\Agent_work\r10\a\xxxxxxxxx.testsettings, here is my

问题 Whats the proper way to form relative file path/ or file path for the runsettings parameter <SettingsFile>xxxxxAutomation.testsettings</SettingsFile> In my local environment this works but when i push it to build release agents it fails since its looking for the file in a different directory which is my release folder but instead its looking for this file in what appears to be in a folder directory. This is the directory its looking at E:\Agent_work\r10\a\xxxxxxxxx.testsettings, here is my

问题 Currently, trying to configure a release pipeline in Azure Devops. I've successfully created a CI pipeline that is working and running tests successfully. My release pipeline uses the artifacts from latest the CI build and should be deploying to azure. When I look at the logs I can see the the following were completed successfully: Initialize Agent Initialize job Download arifact and then the "Deploy to Azure App Service" fails with the logs showing the following details: 2019-02-07T19:06:57

问题 I haven't seen any information how to do a Blue/Green deployment on VSTS Release Definitions. I have a VSTS Release Definition that deploys new changes automatically into our Prod environment as new check-ins are done in our source code. Now, the project is using Azure Traffic Manager and it has added two endpoints which are on different regions/data centers. Now that we have the Azure Traffic Manager configured, I was wondering how can I change on VSTS and at deployment time how Azure

问题 I have a release pipeline which is triggered by CI where I want to push a new version of a nuget package if that version does not exist yet . For that I have a simple command line task which checks whether that nuget is present on nuget.org and stores the result in an environment variable. I can then set the condition for next steps which will only execute the step if that value variable is true. This works all fine, however I wonder how can I simply stop the release process and skip all

问题 What is the process for upgrading the default tasks loaded by Microsoft in an on-premises TFS with no internet connectivity? According to https://docs.microsoft.com/en-us/vsts/build-release/tasks/ there are several tasks now available and supported in TFS v2015-2018/VSTS that do not appear in my TFS 2017u2 installation (specifically the Download Secure File task). The default tasks are not shown in the Manage Extension screens and the git repo (https://github.com/Microsoft/vsts-tasks) does

问题 What is the process for upgrading the default tasks loaded by Microsoft in an on-premises TFS with no internet connectivity? According to https://docs.microsoft.com/en-us/vsts/build-release/tasks/ there are several tasks now available and supported in TFS v2015-2018/VSTS that do not appear in my TFS 2017u2 installation (specifically the Download Secure File task). The default tasks are not shown in the Manage Extension screens and the git repo (https://github.com/Microsoft/vsts-tasks) does

问题 According to https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/pipelines/agents/hosted.md the virtual machine size of the Microsoft-Hosted Agent is: Currently utilizing Microsoft Azure general purpose virtual machine sizes ( Standard_DS2_v2 and Standard_DS3_v2 ) What does that mean? Which size is used? Standard_DS2_v2 or Standard_DS3_v2? Can I decide which one I want to use? Kind regards, Peter 回答1: There isn’t the way to force build/release to use DS3_v2 vm agent, it usually try to

问题 According to https://github.com/MicrosoftDocs/vsts-docs/blob/master/docs/pipelines/agents/hosted.md the virtual machine size of the Microsoft-Hosted Agent is: Currently utilizing Microsoft Azure general purpose virtual machine sizes ( Standard_DS2_v2 and Standard_DS3_v2 ) What does that mean? Which size is used? Standard_DS2_v2 or Standard_DS3_v2? Can I decide which one I want to use? Kind regards, Peter 回答1: There isn’t the way to force build/release to use DS3_v2 vm agent, it usually try to

问题 In VSTS Release, how do I stop all continuous webjobs and remove schedule from triggered webjobs for specific deployment slot? scenario: I have a asp.net core web application with bunch of webjobs. Some of them are scheduled, some are continuous. In VSTS Release I deploy the webjobs together with web app to App Service using Web Deploy. However, in staging environment I don't want to run the webjobs, since they would interfere with production (the share the same database, etc). I guess I