azure-pipelines

问题 I'm new AKS, ACR, and DevOps Pipelines and I'm trying to setup a CI/CD pipeline. I have a resource group setup that has both AKS and ACR in it. AKS is using Standard_B2s and only one node at this point since I'm just playing around. Images are being deployed to ACR automatically on a commit to master--haven't figured out how to setup testing yet--but when it comes to deploying to AKS, I just keep getting a: ##[error]error: deployment "client-deployment" exceeded its progress deadline I've

问题 I just noticed "Approvals and checks" at agent pool level and added couple of checks "approval" and "extend template" check. but it's not working. Same checks if i add at azure devops environments , it works. Is this feature live ? If you have some example then please share 回答1: Extend template check at agent pools in azure pipelines I could reproduce this issue on my side with extends in the YAML file. If I set the following YAML file: trigger: none extends: template: params.yml parameters:

问题 I just noticed "Approvals and checks" at agent pool level and added couple of checks "approval" and "extend template" check. but it's not working. Same checks if i add at azure devops environments , it works. Is this feature live ? If you have some example then please share 回答1: Extend template check at agent pools in azure pipelines I could reproduce this issue on my side with extends in the YAML file. If I set the following YAML file: trigger: none extends: template: params.yml parameters:

问题 I just noticed "Approvals and checks" at agent pool level and added couple of checks "approval" and "extend template" check. but it's not working. Same checks if i add at azure devops environments , it works. Is this feature live ? If you have some example then please share 回答1: Extend template check at agent pools in azure pipelines I could reproduce this issue on my side with extends in the YAML file. If I set the following YAML file: trigger: none extends: template: params.yml parameters:

问题 My Azure pipeline makes use of the Azure CLI task - task: AzureCLI@2 inputs: azureSubscription: '...' scriptType: pscore scriptLocation: 'inlineScript' inlineScript: | containers=$(az storage container list --connection-string '...') The task fails with this error: The term 'containers=$(az storage container list --connection-string '...')' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify

问题 I have a very simple variable substitution in my release pipeline, but it's not working. I have the variable in the connectionStrings.config file as such: <?xml version="1.0"?> <connectionStrings> <add name="ExpenseDBConnectionString" connectionString="__ProdConnString__" providerName="System.Data.SqlClient" /> </connectionStrings> I then have the variable defined in the release pipeline: I also have the XML Variable Substitution enabled in the Deploy Task: But I run the release, and the

问题 How can I use a secret variable in my powershell script in my release definition? I came across this but it doesn't work. The directory "$($env:AGENT_HOMEDIRECTORY)\agent\worker\Modules" doesn't exist on the new agents. What's the correct way of accessing a secret variable on new hosts? My agent version is 2.114.0. 回答1: By design, you have to pass the value of secret variable through PowerShell parameters. For example: Variable: password (secret) task: PowerShell Arguments: -pass $(password)

问题 How can I use a secret variable in my powershell script in my release definition? I came across this but it doesn't work. The directory "$($env:AGENT_HOMEDIRECTORY)\agent\worker\Modules" doesn't exist on the new agents. What's the correct way of accessing a secret variable on new hosts? My agent version is 2.114.0. 回答1: By design, you have to pass the value of secret variable through PowerShell parameters. For example: Variable: password (secret) task: PowerShell Arguments: -pass $(password)

问题 In Azure Pipelines you can set pipeline variables at queue time. You can use such a variable the same way as variables defined by the pipeline itself. Example: # pipeline.yml steps: - checkout: none - template: steps/some.yml parameters: name: $(queueTimeVar) # steps/some.yml parameters: name: 'World' steps: - bash: | echo "Hello ${{ parameters.name }}!" But if the variable isn't set explicitly, the pipeline evaluates this expresstion to the string itself. The step template would be called

问题 In Azure Pipelines you can set pipeline variables at queue time. You can use such a variable the same way as variables defined by the pipeline itself. Example: # pipeline.yml steps: - checkout: none - template: steps/some.yml parameters: name: $(queueTimeVar) # steps/some.yml parameters: name: 'World' steps: - bash: | echo "Hello ${{ parameters.name }}!" But if the variable isn't set explicitly, the pipeline evaluates this expresstion to the string itself. The step template would be called