azure-pipelines-release-pipeline

问题 My release pipeline deploys the application to multiple environments. Based on the environment, I am trying to set up File Transformations to be executed, though I'm not sure how to set it up, if at all possible. I already have the app.Release.config file set up in the repository, but I'm not sure where to go from here. In my release pipelines, I've enabled the native XML Transformation option, but it doesn't actually do anything. I've also tried adding the File Transform task and explicitly

问题 I have a VSTS release pipeline that copies files from a git repo: This git repo is really big - around 1GB in size. Every time I trigger a release, the VSTS agent downloads the entire contents of the git repo. Is there a way to configure VSTS to only download the changes to this git repo, i.e. run a git pull on the repository? This would save a lot of time and bandwidth. 回答1: There are two ways can make the download artifacts step more efficient. Option 1: use PowerShell task to download the

问题 I'm trying to run migration on Azure DevOps Release Pipeline. Because I want to run my DB scripts automatically on every release. My release pipeline does not have source code, I just have compiled DLLs. When I execute this command on my local machine, it runs successfully. How can I convert this command so I can use it with DLLs. dotnet ef database update --project MyEntityFrameworkProject --context MyDbContext --startup-project MyStartupProject 回答1: If you don't want to include your source

问题 In the last 6 months I have been releasing with a pipeline in Azure DevOps, but today I receive the following error: 2019-09-25T14:24:38.4296875Z ##[section]Starting: Azure App Service Deploy: AS-ServiciosNegocio-API-UAT 2019-09-25T14:24:38.4419797Z ============================================================================== 2019-09-25T14:24:38.4419900Z Task : Azure App Service deploy 2019-09-25T14:24:38.4419986Z Description : Deploy to Azure App Service a web, mobile, or API app using

问题 My team are using the VSTS Build & Release mechanism, combined with pull request branch safety settings, so that code can only be merged in when a pull request is completed. We are experiencing something odd though, in that when a pull-request is created (and a build is spawned to prove the commit) - the completion of this build triggered by the pull request also indirectly triggers a release because we have a release trigger setup. This in itself is probably ok, but then what also happens is

问题 My team are using the VSTS Build & Release mechanism, combined with pull request branch safety settings, so that code can only be merged in when a pull request is completed. We are experiencing something odd though, in that when a pull-request is created (and a build is spawned to prove the commit) - the completion of this build triggered by the pull request also indirectly triggers a release because we have a release trigger setup. This in itself is probably ok, but then what also happens is

问题 I am building a Release Pipeline on Azure DevOps. Part of my release is to copy a bunch of files to the Azure VM. As far as I understand, the target machine needs to have PowerShell 5986 port open. I have a VM with port 5986 open (I verified that by invoking remotely some commands on this VM with "PowerShell on Target Machines" task). I added "Windows Machine File Copy" task and filled fields: - Source - Machines - Admin Login - Password - Destination Folder In "Machines" field, I put IP of

问题 I am able to update the variable in the build pipeline using the below json body $body = ' { "definition": { "id": 25 }, "parameters": "{\"var\":\"value\"}" } ' The same json is not working with Release pipeline . Is there any way to pass the variable through same way through release pipeline 回答1: Set Azure devops Release pipeline variable using REST API We could use the REST API Definitions - Get to get all the info about this definition in the body, then we could update the body and use the

问题 I am able to update the variable in the build pipeline using the below json body $body = ' { "definition": { "id": 25 }, "parameters": "{\"var\":\"value\"}" } ' The same json is not working with Release pipeline . Is there any way to pass the variable through same way through release pipeline 回答1: Set Azure devops Release pipeline variable using REST API We could use the REST API Definitions - Get to get all the info about this definition in the body, then we could update the body and use the

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