azure-pipelines-build-task

问题 I am trying to run a PowerShell script present on one of the azure server using the "PowerShell on Target Machines" Task in my TFS build definition, but the task fails with the below error. System.Management.Automation.RuntimeException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name

问题 I've got a .Net Framework 4.6.1 project, which creates a Windows Service. We want to have this built and deployed by an Azure Devops pipeline. We've successfully created pipelines for all of our .Net Core web services (using the ASPNETCORE_ENVIRONMENT variable and a set of appsettings.{ENV}.json files) but the Windows Services don't seem to play as nicely in terms of providing different configuration for different environments. I've got XDT transformations working for the App.config XML file.

问题 Is it possible to publish the output from a build on Visual Studio Team Services to Azure File Storage? I have looked at the Azure File Copy task but can see no way to copy to to anything but Azure Blob Storage or VMs with this. I was thinking I could possibly use AzCopy to achieve this but it seems like this should be supported out of the box. Any ideas? 回答1: From this article, We know that it only support copy files to Azure storage Blog and VMs at currently. I think it does not support at

问题 I have a project on Azure DevOps containing multiple forks of the same main repository. I created a build pipeline for that repository which unfortunately cannot be reused for the present forks since a pipeline can only be configured for a single repository. This solution is not ideal because leads to multiple identical pipelines, one for each fork, and maintaining all of them can be difficult. Is there a way to use one pipeline for multiple repositories? 回答1: you can create a template file

问题 I have a project on Azure DevOps containing multiple forks of the same main repository. I created a build pipeline for that repository which unfortunately cannot be reused for the present forks since a pipeline can only be configured for a single repository. This solution is not ideal because leads to multiple identical pipelines, one for each fork, and maintaining all of them can be difficult. Is there a way to use one pipeline for multiple repositories? 回答1: you can create a template file

问题 I'm trying to send a detailed email containing information about all failed unit tests in a pipeline and said email must be sent to the developer who wrote the unit tests. Currently, I have a Visual Studio Test task in my build pipeline which executes my tests and sends an email on failure which provides at least some information. However: a) I would like the email to be be send to the developer who wrote the tests. b) Email should contains all the details of the tests that failed (such as

问题 I created a new extension for TFS following MS tutorial. For some reason when I'm adding Icon to my extension I can see this icon when I'm installing the extension and in the "Extension Manager" page, But when I choose my extension from the build step menu the image is missing . In the "vss-extension.json" file I added: "icons": { "default": "images/icon.png" }, "files": [ { "path": "images", "addressable": true }, { "path": "dist", "addressable": true, "packagePath": "scripts" }, { "path":

问题 I have a Microsoft Visual Studio Team Foundation Server (Version 15.117.26714.0) with predefined variable $(ProjectBuildNumber). Is there any way to increment, during build process, value of variable with minor build number by +1? $(ProjectBuildNumber) = 663 So, that on next build it will be: $(ProjectBuildNumber) = 664 回答1: You can't reference variables in the build number of the Build Definition. But what you can do is override the build number in the build itself. You can either use a

问题 I've been fighting with this for over a day now. I have a simple requirement inside of a VSTS CI/CD pipeline that I'm trying to build that any branch following the pattern release/* or hotfix/* should trigger a deployment to my QA environment. Here is my branch based configuration: This configuration does not trigger the deployment as expected. As you can see in the screenshot below the release ran but did not trigger against any of my environments. (QA is the second grey square from the

问题 I need guidance in generating code coverage report of Asp.net unit tests in azure build pipeline. My project is based on .Net Framework 4.6. I am able to run all the unit tests using "visual studio test" task. I tried the "report generator" task, but it require cobertura or jacoco etc xml files, which am unable to generate in the build pipeline. Expectation - I want to get code coverage report for the runned unit tests which will show complete information like the lines coverage, branch