azure-pipelines

问题 In an Azure DevOps pipeline template, I am declaring a parameter as an array/sequence parameters: mySubscription: '' myArray: [] steps: - AzureCLI@2 inputs: azureSubscription: ${{ parameters.mySubscription }} scriptType: pscore scriptPath: $(Build.SourcesDirectory)/script.ps1 arguments: '-MyYAMLArgument ${{ parameters.myArray }}' Value for the parameter is then passed from pipeline definition as steps: - template: myTemplate.yml parameters: mySubscription: 'azure-connection' myArray: - field1

问题 In an Azure DevOps pipeline template, I am declaring a parameter as an array/sequence parameters: mySubscription: '' myArray: [] steps: - AzureCLI@2 inputs: azureSubscription: ${{ parameters.mySubscription }} scriptType: pscore scriptPath: $(Build.SourcesDirectory)/script.ps1 arguments: '-MyYAMLArgument ${{ parameters.myArray }}' Value for the parameter is then passed from pipeline definition as steps: - template: myTemplate.yml parameters: mySubscription: 'azure-connection' myArray: - field1

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

问题 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'm new to DevOps so please go easy on me if I've missed something basic :) I’m using the following in Azure Pipelines: Hosted MacOS with an Xcode Build Agent (Xcode Version 5.142.0) I've just started trying to set up a pipeline for an Xcode based project which uses multiple provisioning profiles. In my scenario I have profiles for the following in my app: Intents ItentsUI Widget App I've followed the instructions for setting up certs and provisioning profiles here (although my project uses

问题 I'm new to DevOps so please go easy on me if I've missed something basic :) I’m using the following in Azure Pipelines: Hosted MacOS with an Xcode Build Agent (Xcode Version 5.142.0) I've just started trying to set up a pipeline for an Xcode based project which uses multiple provisioning profiles. In my scenario I have profiles for the following in my app: Intents ItentsUI Widget App I've followed the instructions for setting up certs and provisioning profiles here (although my project uses

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