azure-pipelines

问题 I am working on a project to develop an Azure DevOps release task extension. Recently, I am getting this warning message printed multiple times in the logs when the release task runs- "Warning: Use Cipheriv for counter mode of aes-256-ctr". I was not getting it earlier. And the time when I started getting this error, I only changed some console.log(..), and not even any code that could possibly trigger this error. (Might be some npm dependency updates!) Any idea regarding why am I getting

问题 I am working on a project to develop an Azure DevOps release task extension. Recently, I am getting this warning message printed multiple times in the logs when the release task runs- "Warning: Use Cipheriv for counter mode of aes-256-ctr". I was not getting it earlier. And the time when I started getting this error, I only changed some console.log(..), and not even any code that could possibly trigger this error. (Might be some npm dependency updates!) Any idea regarding why am I getting

问题 I currently have a monorepo with services in subdirectories that I'm leaning towards turning into a multirepo with a metarepo. One of the reasons I decided to give Azure DevOps a try was someone told me you can have triggers on the subdirectories like: trigger: branches: include: - master paths: include: - client Tested and it works. However, what I'm wondering is if it possible to have multiple independent triggers, or does this require either a polyrepo or multiple .yml ? The reason being

问题 I currently have a monorepo with services in subdirectories that I'm leaning towards turning into a multirepo with a metarepo. One of the reasons I decided to give Azure DevOps a try was someone told me you can have triggers on the subdirectories like: trigger: branches: include: - master paths: include: - client Tested and it works. However, what I'm wondering is if it possible to have multiple independent triggers, or does this require either a polyrepo or multiple .yml ? The reason being

问题 I googled last few days to get the list of input types supported by VSTS Task plugin, but don't get anything appropriate. Is this possible to create Grid in task plugin 回答1: At present, there is no way to create a Grid on the task input page. For a complete list of the supported types, take a look at the Reference for creating custom build tasks within extensions for details. This is schema definition for what your custom task JSON needs to conform to. If you look under inputs/items

问题 I've started doing some testing using multi-stage pipelines to be able to have the pipeline as code, but I'm getting a bit confused about the usage of the pipeline considering we have Release pipeline as well, and multi-stage pipeline currently can do the release pipeline's job with gates and multiple environments, just in a code based pipeline which I would prefer. My question is when should each of them be used? 回答1: When should each of them be used? Here, very agree iberodev and Daniel's

问题 I'm trying to create new build pipeline through programmatically. I'm looking for Azure DevOps REST API for this action. I didn't get the proper examples for creating the pipeline using REST API. Please advise. 回答1: How to create new build pipeline using Azure DevOps REST API? To create the new build pipeline, we could use the REST API Definitions - Create: POST https://dev.azure.com/{organization}/{project}/_apis/build/definitions?api-version=5.0 But we need provide too much information in

问题 Whats the proper way to form relative file path/ or file path for the runsettings parameter <SettingsFile>xxxxxAutomation.testsettings</SettingsFile> In my local environment this works but when i push it to build release agents it fails since its looking for the file in a different directory which is my release folder but instead its looking for this file in what appears to be in a folder directory. This is the directory its looking at E:\Agent_work\r10\a\xxxxxxxxx.testsettings, here is my

问题 Whats the proper way to form relative file path/ or file path for the runsettings parameter <SettingsFile>xxxxxAutomation.testsettings</SettingsFile> In my local environment this works but when i push it to build release agents it fails since its looking for the file in a different directory which is my release folder but instead its looking for this file in what appears to be in a folder directory. This is the directory its looking at E:\Agent_work\r10\a\xxxxxxxxx.testsettings, here is my

问题 I have installed 3 different versions of Ruby in self hosted agent but i am unable to use them in my vsts task as required. The microsoft document suggests configuring " Agent.ToolsDirectory " but i am not sure how to configure it in the self hosted agents. Can anyone help me with descriptive steps on how to configure it so that i can use the vsts task : "Use Ruby Version task" on my self hosted agent 回答1: how to configure it in the self hosted agents? Agent.ToolsDirectory , this is one of