azure-pipelines

Azure devops pipelines conditional name

陌路散爱 提交于 2020-03-01 02:11:45
问题 I am using azure-devops pipelines but I am having problems to set the name of the build. Here is a normal build definition. pool: vmImage: 'VS2017-Win2016' name: myBuildName steps: - task: NuGetToolInstaller@0 - task: NuGetCommand@2 inputs: restoreSolution: '$(solution)' What I would like to do is to set the name with a conditional check. If (something) then X otherwise Y I have checked the conditional documents, but no luck. Here is what I would like to do, but obviously does not work # if

In Azure DevOps Server 2019 (on-prem) release pipeline how can one stage pass a file to another stage?

只谈情不闲聊 提交于 2020-02-25 04:00:58
问题 We have Azure DevOps Server 2019 on-prem. That means no unified pipelines, no YAML for release pipeline. The scenario is this: A stage runs terraform code to provision some resources in Azure. It is necessary to insert manual approval between terraform plan and terraform apply , however, the plan file produced by terraform plan stage must be shared with the terraform apply stage. I can see these options: Save the plan file on a shared file system Save the plan file in a dedicated storage on

In Azure DevOps Server 2019 (on-prem) release pipeline how can one stage pass a file to another stage?

我是研究僧i 提交于 2020-02-25 04:00:25
问题 We have Azure DevOps Server 2019 on-prem. That means no unified pipelines, no YAML for release pipeline. The scenario is this: A stage runs terraform code to provision some resources in Azure. It is necessary to insert manual approval between terraform plan and terraform apply , however, the plan file produced by terraform plan stage must be shared with the terraform apply stage. I can see these options: Save the plan file on a shared file system Save the plan file in a dedicated storage on

How to fix 'Error processing method: 'System.Void Prism.Navigation.PageNavigationService' error in Azure Pipelines

|▌冷眼眸甩不掉的悲伤 提交于 2020-02-23 07:25:50
问题 After updating Prism NuGet package 7.2.0.1367 to my Xamarin.Forms project, Azure pipelines fails to build. The local build succeeds as does App Center build. I'm getting the following error in Azure Pipelines : "/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(2053,5): error MSB4018: Mono.Linker.MarkException: Error processing method: 'System.Void Prism.Navigation.PageNavigationService::ConfigureTabbedPage(Xamarin.Forms.TabbedPage,System.String

Export tests results from Azure DevOps

心已入冬 提交于 2020-02-23 06:21:27
问题 I might be missing something, but can't find a way to export tests run results from the project's build pipeline execution page in Azure DevOps. There is a " Download logs " option, of cause, where you technically can find logs from tests execution step as well among other things, but that doesn't seems to be the best/proper way to get that kind of data on a regular basis for regulations/audit/documentation purpose compared to how it is possible to get test results from other build systems

How to unpack or fetch a value of a nested variable stored in Azure DevOps Build Piplines' Variables group?

…衆ロ難τιáo~ 提交于 2020-02-22 05:36:10
问题 Is it possible to use variable inside a variable in Powershell script with Azure Pipelines variables? SCENARIO Two variables are set in Azure Pipelines Variable group - DeploymentCredentials a. DeployUATApiPassword = "123456" b. DeployPRODApiPassword = "789654" Another variable is set in the Variables section of the pipeline as DeploymentEnvironment At runtime, the value of the DeploymentEnvironment variable is set as either UAT or PROD Based on the enviornment, I want to fetch the password

How do I get my Azure DevOps Pipeline build to fail when my linting script returns an error?

℡╲_俬逩灬. 提交于 2020-02-22 03:13:41
问题 I am using the Azure Pipelines GitHub add-on to ensure that pull requests pass my linting. However, I have just made a test pull request which fails my linting, but the Azure Pipeline succeeds. Here is my azure-pipelines.yml # Node.js with React # Build a Node.js project that uses React. # Add steps that analyze code, save build artifacts, deploy, and more: # https://docs.microsoft.com/azure/devops/pipelines/languages/javascript trigger: - master pool: vmImage: 'Ubuntu-16.04' steps: - task:

How do I get my Azure DevOps Pipeline build to fail when my linting script returns an error?

淺唱寂寞╮ 提交于 2020-02-22 03:02:06
问题 I am using the Azure Pipelines GitHub add-on to ensure that pull requests pass my linting. However, I have just made a test pull request which fails my linting, but the Azure Pipeline succeeds. Here is my azure-pipelines.yml # Node.js with React # Build a Node.js project that uses React. # Add steps that analyze code, save build artifacts, deploy, and more: # https://docs.microsoft.com/azure/devops/pipelines/languages/javascript trigger: - master pool: vmImage: 'Ubuntu-16.04' steps: - task:

Azure DevOps: Console output for green tests is missing

与世无争的帅哥 提交于 2020-02-20 08:36:26
问题 We migrated our NUnit tests execution from TeamCity to Azure DevOps. One of the biggest issues so far - there is no way to see Console output for green (passed) tests. Is this basic feature really missing in DevOps, or I simply do not know where to look? Here is how to view Console output for failed tests: UPDATE : In the documentation there is a "Tip" (https://docs.microsoft.com/en-us/azure/devops/pipelines/test/review-continuous-test-results-after-build?view=azure-devops): If you use the

Nuget package description in the Azure DevOps Nuget pipeline step

↘锁芯ラ 提交于 2020-02-16 06:30:34
问题 Is it possible to add a description for the NuGet package being added in the Azure DevOps Pipeline? 回答1: Nuget package description in the Azure DevOps Nuget pipeline step As we know, when we pack the nuget package with .csproj file, nuget will get the package info from the file AssemblyInfo.cs in the project, like assembly: AssemblyVersion , assembly: AssemblyDescription and so on. So, to add a description for the NuGet package, we could add the description for assembly: AssemblyDescription