azure-devops

问题 I have both server side (web api using c#) and client side (angular) code in same branch. I have created separate stage for both server side and client side code to build, and one more stage to deploy. If I check in code in either of client side or server side the all the 3 stages run. To avoid this I am looking for ways to add conditions at stage level so that if there are server side changes then only Server stage will run, if the checked in code has only client side code then only Client

问题 At the company, we will change the URL for the Azure Devops workspace from https://oldname.visualstudio.com to https://dev.azure.com/newname . We have a lot of connections to Slack in Azure DevOps using two approaches. Older links via service hooks in Azure Devops, new links are via slack applications Azure Repos and Azure Pipelines. Service hooks in Azure DevOps use Slack's Incoming webhooks, so they will not be affected. However, Microsoft prefers to use its Slack Azure Repos and Azure

问题 I have the exact same pipeline in two different branches of the same repository, stage and prod . I'd like the pipeline on branch stage to run when a tag starting with stage@ is created (e.g. stage@1.0.1 ); similarly, I'd like the pipeline on branch prod to run when a tag starting with prod@ is created (e.g. prod@1.0.1 ). In branch stage , trigger is defined like this: # .azure-pipelines.yml [refs/branches/stage] trigger: tags: include: - stage@* In branch prod , trigger is defined like this:

问题 I have the exact same pipeline in two different branches of the same repository, stage and prod . I'd like the pipeline on branch stage to run when a tag starting with stage@ is created (e.g. stage@1.0.1 ); similarly, I'd like the pipeline on branch prod to run when a tag starting with prod@ is created (e.g. prod@1.0.1 ). In branch stage , trigger is defined like this: # .azure-pipelines.yml [refs/branches/stage] trigger: tags: include: - stage@* In branch prod , trigger is defined like this:

问题 I am trying to install a pip package from Azure Artifacts as part of a Docker image(with Docker@2 task) but whatever I try does not work. It looks like my pip inside Docker cannot authenticate against Azure Artifacts whatever I try. Closest I got is with RUN pip install keyring artifacts-keyring ENV ARTIFACTS_KEYRING_NONINTERACTIVE_MODE true RUN pip install <> --index-url https://pkgs.dev.azure.com/<>/_packaging/<>/pypi/simple/ but in my Azure devops, i keep getting ERROR: Could not find a

问题 I am trying to install a pip package from Azure Artifacts as part of a Docker image(with Docker@2 task) but whatever I try does not work. It looks like my pip inside Docker cannot authenticate against Azure Artifacts whatever I try. Closest I got is with RUN pip install keyring artifacts-keyring ENV ARTIFACTS_KEYRING_NONINTERACTIVE_MODE true RUN pip install <> --index-url https://pkgs.dev.azure.com/<>/_packaging/<>/pypi/simple/ but in my Azure devops, i keep getting ERROR: Could not find a

问题 I want to package and publish a .net standard based code as a nuget package using VSTS build. I have created a private nuget feed (in VSTS Artifacts) to which I would like to publish nuget package along with symbols package. I tried using dotnet CLI tasks to build and publish but it only publish .nupkg and not *.snupkg to the nuget feed. I googled alot but I only found articles related to publishing to nuget.org and not to a private feed. 回答1: Publish *.snupkg symbol package to private feed

问题 Our builds fails intermittently without any error message other than Exit code -1 returned from process: file name 'C:\agent\vsts-agent-win-x64-2.129.0\externals\node\bin\node.exe' We have two build agents hosted on our own VM's in Azure. They are hosted inside an App Service Environment (ASE) so that they can deploy to App Services inside the ASE. This happens on any of our two build agents, and on different vsts tasks: npm test: Exit code -1 returned from process: file name 'C:\agent\vsts

问题 We are using VSTS for our CI/CD environment. In our project we have multiple parts, like Database and Frontend1, which have a separate folder in our repository: src/ Database Frontend1 ... I have created a separate build for each of the components of our project, which are triggered if there changes pushed to the corresponding subfolder. I want this separation to easily control and check the version of each component. Database --> Build Database Frontend1 --> Build Frontend1 With this

问题 I have an Azure DevOps Build Pipeline which contains two Agent Jobs, which I'll call Job A and Job B. I want these jobs to run simultaneously, but if Job A fails, then I don't need Job B to run to completion. Is there any way to add a task to Job A which will cancel Job B (or, alternately, terminate the entire pipeline with a "Failed" status) if any of Job A's tasks failed? 回答1: Add a PowerShell task that cancel the pipeline when a task failed: steps: - powershell: | Write-Host "Cancel all