azure-pipelines

问题 I am working to build a ci/cd pipeline for AKS. the first task set is "Azure resource group deployment" which is used for creating vnet /subnet for the AKS . The intention is to skip the task next time onwards since the vnet and subnet are already in place. Second time onwards getting the following error - BadRequest: { "error": { "code": "InUseSubnetCannotBeDeleted", "message": "Subnet AKSSubnet is in use by /subscriptions/***************************************/resourceGroups/MC_***********

问题 This questions is related to the one here I am trying to put up a dialog box to show the author at the time a pull request is created in my Azure DevOps service. This box should be shown in the author's browser window like so: Have you run System tests? Yes Not applicable Here's the code I have at the moment, just trying to show a dummy Message Box #r "Newtonsoft.Json" using System; using System.Net; using System.Net.Http; using System.Net.Http.Headers; using System.Text; using Newtonsoft

问题 This questions is related to the one here I am trying to put up a dialog box to show the author at the time a pull request is created in my Azure DevOps service. This box should be shown in the author's browser window like so: Have you run System tests? Yes Not applicable Here's the code I have at the moment, just trying to show a dummy Message Box #r "Newtonsoft.Json" using System; using System.Net; using System.Net.Http; using System.Net.Http.Headers; using System.Text; using Newtonsoft

问题 This question is closely linked to the one here Given, that I am opting to go for Release Flow and Trunk based Development in Azure DevOps, how should I be arranging my pipelines and yamls (pseudocode yaml). Here is what I think based on the previous SO question above. -Branch dev -yaml - dev.yml (trigger: dev, features/*) for pipeline Development - R1.0.yml (trigger: release/R1.0, bugfix/R1.0/*, hotfix/R1.0/*, features/R1.0/*) for pipeline ReleaseR1.0 -Branch R1.0 -yaml - dev.yml (trigger:

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 2 years ago . I have .Net Solution project it has multiple projects few of them are console application. I want to execute one of the console application during my release pipeline as task under empty process. How can I refer the .exe from my build artifact? 回答1: Add "Command Line" task during

问题 I have a Tests step in my pipeline. I want that step to run all tests on scheduled runs but only impacted Tests on manual or gated runs. To do this, I linked the runOnlyImpactedTests value to a process variable and I'm trying to modify its value using Powershell. I'm able to read the variable but I can't change it. I have two questions but first, here are the PS scriptlet Write-Host "a ${Env:Parameters_runOnlyImpactedTests} b" Write-Host "##vso[task.setvariable variable=Parameters

问题 When using YAML for builds, I could not find how to give an instruction that refers to the variable group I want to use. I had to manually open my build definition in the VSTS builds UI and create the link. Does anyone know how to refer the variable group through the YAML? 回答1: Unfortunately we cannot link variable group through YAML for now. There is a user voice here submitted to suggest the similar feature, you can go and vote it up or submit a new one to suggest that again to achieve that

问题 I'm trying to build a Docker image, which seems to build and run fine on my local machine, but it keeps failing with the following error: 2018-05-06T13:56:15.2331697Z failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\docker\windowsfilter\3b555fe81a5123419e06c66652d9e73adbbb17b10f52ddd9f59da3b7fb87adab\UtilityVM: The system cannot find the path specified. 2018-05-06T13:56:15.2531044Z ##[error]C:\Program Files\Docker\docker.exe failed with

问题 Approx 50% of my hosted builds are failing with npm error 134. I am building the same commit with the same build definition using hosted vs2017. I am building an Angular Application using the Angular CLI. The npm task calls 'run build' which is defined as "ng build --prod" in my package.json. Both a successful build and failed build are using npm task version 1.1.49 and npm verion 6.8. This leads me to believe it is something related to the hosted environment. The hosted vs2017 and vs2019

问题 Approx 50% of my hosted builds are failing with npm error 134. I am building the same commit with the same build definition using hosted vs2017. I am building an Angular Application using the Angular CLI. The npm task calls 'run build' which is defined as "ng build --prod" in my package.json. Both a successful build and failed build are using npm task version 1.1.49 and npm verion 6.8. This leads me to believe it is something related to the hosted environment. The hosted vs2017 and vs2019