azure-pipelines

问题 i have one solutions with multiple projects. DSS.DMN.Client project dependens on other projects(have references) This is how my yaml files looks like - task: MSBuild@1 displayName: 'Build solution Client' inputs: platform: anyCPU maximumCpuCount: true configuration: 'Integration' solution: DSS.DMN.Client - task: CopyFiles@2 inputs: SourceFolder: '$(Build.SourcesDirectory)' Contents: '**\bin\**' TargetFolder: '$(Build.ArtifactStagingDirectory)' - task: PublishBuildArtifacts@1 displayName:

问题 How does one pass the build version (say v 1.2.3 ) from an Azure DevOps Build Pipeline to/through the Artifact to the Release? Ideally we would like our build number (in package.json) to match the release name or rather our release name should reflect the build number/semantic version. A manual solution where we enter the version number when creating the release is also acceptable. The release has a Release Name format which is set to Parts-$(Build.Buildnumber) . We can see no way to use

问题 I am in an enterprise that creates many large to small scale applications. Way back when I started using Visual Studio Online/VSTS/now Azure devops I broke all of these apps out into different projects. However, now it seems there is good support for managing multiple apps in one project, and this seems easier from a management standpoint. From the research I did it seems i can do each service individually: Repos : Select Import Repository from the consolidated project and enter in the URL of

问题 I have a repository with two solutions in it. Both solution files exist in the root directory, essentially like this: /WebsiteOneDirectory/ /WebsiteTwoDirectory/ /.gitignore /WebsiteOne.sln /WebsiteTwo.sln Is it possible for me to build multiple pipelines pointed at this repository to build the different solutions? When I create my first pipeline it is generating a azure-pipelines.yml file for the repo, so I am unsure how/if I am going to be able to have multiple pipeline configurations if

问题 I have a repository with two solutions in it. Both solution files exist in the root directory, essentially like this: /WebsiteOneDirectory/ /WebsiteTwoDirectory/ /.gitignore /WebsiteOne.sln /WebsiteTwo.sln Is it possible for me to build multiple pipelines pointed at this repository to build the different solutions? When I create my first pipeline it is generating a azure-pipelines.yml file for the repo, so I am unsure how/if I am going to be able to have multiple pipeline configurations if

问题 Need to create a CICD pipeline with yaml using TFVC repository. 回答1: See this doc: Two types of repositories the pipelines supported. Until now, the YAML only support the repository of git type, and we haven't expand the feature and YAML grammer to support the YAML for TFVC repository. Since only one workaround is migrate your repository from TFVC to Git, but I could not sure whether it is feasible for you to do migrate, especially if your repository is a bit old. If repos is little old,

问题 Need to create a CICD pipeline with yaml using TFVC repository. 回答1: See this doc: Two types of repositories the pipelines supported. Until now, the YAML only support the repository of git type, and we haven't expand the feature and YAML grammer to support the YAML for TFVC repository. Since only one workaround is migrate your repository from TFVC to Git, but I could not sure whether it is feasible for you to do migrate, especially if your repository is a bit old. If repos is little old,

问题 The bounty expires in 4 days . Answers to this question are eligible for a +50 reputation bounty. scniro is looking for a canonical answer : is this supported or not - looking for authoritative source I'm setting up a pipeline using Azure Pipelines YAML format. I have created 3 stages: Build, Staging, and Production. As the names suggest, the Build stage builds the project and publishes the build artifacts. The Staging stage deploys to the Staging environment and the Production stage deploys

问题 I have an application that uses .NET Core 3.1 but in .NET Core Build and Publish tasks, the dropdown menu offers only 'til 2.x version. How am I supposed to use them or what workaround instead? Simple CLI? Thanks in advance @Patrick .NET Core Task is this right? But how should be that different compared to Restore/Build/Publish that are aldready set up in .NET Core pipeline? If that so, I guess I just need to set the command with my custom publish value: dotnet publish myPath -c release -f

问题 I am trying to deploy a react app I created with create-react-app locally to azure. I am trying to do this with azure pipelines. The code I have so far: # Node.js React Web App to Linux on Azure # Build a Node.js React app and deploy it to Azure as a Linux web app. # Add steps that analyze code, save build artifacts, deploy, and more: # https://docs.microsoft.com/azure/devops/pipelines/languages/javascript trigger: - master - azure-pipelines variables: # Azure Resource Manager connection