Azure DevOps Build Pipeline 适用于具有多种项目类型的解决方案

我有一个包含以下内容的解决方案

• 几个 Asp.net 项目（微服务和网关）

• .Net Core + Angular 8（前端）

当我点击 Visual Studio 中的构建按钮时，每个项目都会构建。我已经创建了一个存储库并上传了解决方案。现在，我试图弄清楚如何设置管道来构建每个微服务并将其部署到单独的 Azure Web 应用程序。

我有以下 Angular 项目的管道。我应该像这样定义单独的任务吗？有没有办法在这里复制 Visual Studio 构建？

# ASP.NET
# Build and test ASP.NET projects.
# Add steps that publish symbols, save build artifacts, deploy, and more:
# https://learn.microsoft.com/azure/devops/pipelines/apps/aspnet/build-aspnet-4

trigger:
- master

pool:
  vmImage: 'windows-latest'

variables:
  solution: '**/*.sln'
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release'

steps:
- task: NuGetToolInstaller@1

- task: Npm@1
  inputs:
    command: install
    workingDir: 'd:\a\1\s\Ok.Web\ClientApp'

- task: Npm@1
  inputs:
    command: custom
    workingDir: 'd:\a\1\s\Ok.Web\ClientApp'
    customCommand: run build

- task: CopyFiles@2
  inputs:
    targetFolder: '$(Build.ArtifactStagingDirectory)'    

- task: PublishBuildArtifacts@1

您可以在此处应用两种方法之一：

1. 整个仓库的一条管道
2. 项目一条管道

在这两种情况下，您都可以使用模板来避免重复；因此，您将定义构建 .NET 项目的常见任务，然后在管道中使用它们。我最近发表了一篇关于this http://thecodemanual.pl/2020/04/02/build-templates-on-azure-devops.html，但请看一下文档 https://learn.microsoft.com/en-us/azure/devops/pipelines/process/templates?view=azure-devops too.

为了实现这一点，您需要首先定义一个包含常见步骤的 YAML 文件。例如：

parameters:
- name: buildConfiguration # name of the parameter; required
  default: 'Release'
- name: projectFolder
  default: ' '

steps:

- task: DotNetCoreCLI@2
  displayName: Restore nuget packages
  inputs:
    command: restore
    projects: '*.csproj'
    workingDirectory: '${{ parameters.projectFolder}}'

- task: DotNetCoreCLI@2
  displayName: Build
  inputs:
    command: build
    projects: '${{ parameters.projectFolder}}'
    arguments: '--configuration ${{ parameters.buildConfiguration }}'

# You just added coverlet.collector to use 'XPlat Code Coverage'
- task: DotNetCoreCLI@2
  displayName: Test
  inputs:
    command: test
    projects: '*Tests/*.csproj'
    arguments: '--configuration ${{ parameters.buildConfiguration }} --collect:"XPlat Code Coverage" -- RunConfiguration.DisableAppDomain=true'
    workingDirectory: '${{ parameters.projectFolder}}'

- task: DotNetCoreCLI@2
  inputs:
    command: custom
    custom: tool
    arguments: install --tool-path . dotnet-reportgenerator-globaltool
  displayName: Install ReportGenerator tool

- script: ./reportgenerator -reports:$(Agent.TempDirectory)/**/coverage.cobertura.xml -targetdir:${{ parameters.projectFolder}}/coverlet/reports -reporttypes:"Cobertura"
  displayName: Create reports

- task: PublishCodeCoverageResults@1
  displayName: 'Publish code coverage'
  inputs:
    codeCoverageTool: Cobertura
    summaryFileLocation: ${{ parameters.projectFolder}}/coverlet/reports/Cobertura.xml  

然后从主构建文件中调用此文件：

variables:
  buildConfiguration: 'Release'
  projectFolder: 'path to your project'

steps:

- template: build-and-test.yaml
  parameters:
      buildConfiguration: $(buildConfiguration)

- script: echo Some steps to create artifacts!
  displayName: 'Run a one-line script'

在方法 1 中，即使只更改一个项目，您也将构建所有项目，因此我建议您使用方法 2。为此，您可以定义多个管道（每个项目一个）并将触发器限制为特定文件夹中的更改。请看一下.

这里有一个示例，说明如何将触发器限制到主分支的特定文件夹：

trigger:
  branches:
    include:
    - master
  paths:
    include:
    - gated-checkin-with-template/*
    exclude:
    - gated-checkin-with-template/azure-pipelines-gc.yml