基于VSTS的Azure多Web项目CI/CD：同一App Service批量部署可行性咨询

Great questions! Let’s break them down clearly based on Azure DevOps (formerly VSTS) and Azure App Service best practices:

1. Can I deploy multiple projects to the same App Service? #

By default, an Azure App Service is designed to host a single primary web application, but you can deploy multiple projects to the same App Service using these common approaches:

• Virtual Applications (ideal for same-tech-stack projects)
  This is the most straightforward method for projects built on the same framework (like multiple ASP.NET apps). Here's how it works:

  1. In the Azure Portal, navigate to your App Service > Configuration > Path mappings.
  2. Add a new Virtual Application for each project, specifying a virtual path (e.g., /project1) and a physical path relative to site\wwwroot (e.g., site\wwwroot\project1).
  3. In your Azure DevOps deployment task, set the Virtual Application field to the corresponding path for each project. This will deploy each project to its own isolated subpath within the same App Service.
     Note: Ensure your projects' configuration files (like web.config) don’t conflict with each other.

• Containerized deployment (for mixed-tech-stack projects)
  If your projects use different frameworks (e.g., one ASP.NET, one Node.js), you can package each project into a separate container image, then use an Azure App Service configured for container deployment. However, this requires more setup (like managing container registries and orchestrating multi-container deployments) compared to virtual applications.

2. Can I batch deploy all Web App projects without creating tasks one by one? #

Absolutely! You don’t need to manually create a deployment task for each project. Use these approaches in Azure DevOps to automate batch deployments:

Option 1: Matrix Strategy in YAML Pipelines #

This is the cleanest method for YAML-based pipelines. Define your project list, then use a matrix to generate deployment tasks dynamically:

variables:
  # List all your feature sub-project paths
  projects: ['feature/project1', 'feature/project2', 'feature/project3']

stages:
- stage: DeployAllProjects
  jobs:
  - job: Deploy
    strategy:
      matrix:
        # Generate a job for each project (replace slashes to avoid invalid job names)
        ${{ each project in variables.projects }}:
          ${{ replace(project, '/', '_') }}:
            projectPath: ${{ project }}
            projectName: ${{ replace(project, 'feature/', '') }}
    steps:
    - task: AzureWebApp@1
      inputs:
        azureSubscription: '<Your Azure Service Connection>'
        appType: 'webApp'
        appName: '<Your App Service Name>' # Use a variable here if deploying to different App Services
        package: '$(Build.ArtifactStagingDirectory)/$(projectPath)/*.zip'
        virtualApplication: '/$(projectName)' # Omit if deploying to separate App Services

Option 2: Dynamic Task Generation with PowerShell (for classic or YAML pipelines) #

If you prefer a script-driven approach, use PowerShell to auto-discover your feature sub-projects and generate deployment tasks on the fly:

steps:
# Step 1: Discover all sub-projects in the feature folder
- task: PowerShell@2
  name: DiscoverProjects
  inputs:
    targetType: 'inline'
    script: |
      $projectFolders = Get-ChildItem -Path $(System.DefaultWorkingDirectory)/feature -Directory | Select-Object -ExpandProperty Name
      $jsonOutput = $projectFolders | ConvertTo-Json
      Write-Host "##vso[task.setvariable variable=projectList]$jsonOutput"

# Step 2: Deploy each discovered project
- ${{ each project in ConvertFrom-Json(variables.projectList) }}:
  - task: AzureWebApp@1
    displayName: Deploy ${{ project }}
    inputs:
      azureSubscription: '<Your Azure Service Connection>'
      appType: 'webApp'
      appName: '<Your App Service Name>'
      package: '$(Build.ArtifactStagingDirectory)/feature/${{ project }}/*.zip'
      virtualApplication: '/${{ project }}'

Key note: Make sure your build pipeline packages each feature sub-project into its own zip file and publishes them to the artifact staging directory so the deployment tasks can locate them.

内容的提问来源于stack exchange，提问作者arjunan