azure-pipelines

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

问题 I have an Azure pipeline, which works pretty well with a self-signed certificate: It deploys (via ARM templates) Redis, CosmosDB, EventHub, Keyvault, then imports the self-signed certificate into the Keyvault, then deploys SF cluster and configures it with the certificate. Finally the pipeline deploys our team's application with the following task: - task: ServiceFabricDeploy@1 displayName: 'Deploy SF app' inputs: applicationPackagePath: '$(Build.BinariesDirectory)\Release\Applications

问题 I have a Visual Studio setup project. Normally I use the Microsoft Visual Studio Installer Projects extension, and run an MSBuild Exec task with command line using devenv. This works on my dev box and my existing build machine. However I'm looking to migrate to a hosted pipeline agent using the VS2017 image. I was hoping the installer extension might already be installed, so I tried my build and got an error: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv

问题 Im struggling to find any documentation to select a specific build agent that's in a given pool via our yaml azure pipeline file. Right now were selecting the pull to launch the job on but I'm having massive deployment issues with our servers and need to individually select the one I want to run the job on have anyone ever had to do something like this before? trigger: batch: true branches: include: - master paths: exclude: - README.md pool: 'ZupaDeploymentPool' 回答1: You can use Demands to

问题 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 plenty of bash scripts with various variables that being piped into various scripts. I've been wondering if I can extract an output of bash script that is activated by Azure Pipeline to be a pipeline variable for the rest of the Pipeline runtime? Example: foo=$(date + %Y%m%d_%H%M%S) output: 20200219_143400, I'd like to get the output for later use on the pipeline. 回答1: Depends on how you design your pipeline you can use Azure Pipeline variables: Inside the same Job: - job: Job1 steps:

问题 I have a PowerShell script task that gets the names of some files from a folder in my git repo and puts them into a variable. I want to use those file names in parameters and use "each" condition in another task (task: HelmDeploy@0) in order to run that task each time with one of the file names as valueFile variable. Here is what I have tried, however it gives an error Template-Yaml/deploy-jobs.yaml@pipelinetemplates Expected a sequence or mapping. Actual value '$[dependencies.A.outputs[

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

问题 In Azure Devops when your Maven build task fails it will display an an error like below in the build summary: Maven build error Now if you click in and scroll up you will be able to find the error next to the reactor summary. This is easy enough to do at home with a mouse and a big screen but for some of our devs on trains or in cafes it can be quite an effort for them to find the error. I want to be able to make the error easier to find. Some suggestions I've thought of but not sure how to