能否将每个Pull Request部署至带唯一URL的App Service？

Absolutely! This is a super common (and extremely useful) workflow for teams wanting to share in-progress work with designers, stakeholders, or QA early on. The default PR-Branch Triggers do have limitations around overwriting deployments, but we can work around that by dynamically creating unique deployment targets for each PR.

Core Approach: Dynamic, PR-Specific Deployment Targets #

Instead of deploying all PRs to the same environment, we’ll create a unique deployment slot (or even a full App Service instance) for each PR, named using the PR number or branch name. This ensures no overwrites and gives you a dedicated, shareable URL for every feature/bugfix branch.

Option 1: Use Azure App Service Deployment Slots (Cost-Effective & Recommended) #

Deployment slots are perfect here—they share the same App Service plan, so you don’t incur extra costs for basic hosting, and each slot gets its own unique URL.

Step-by-Step Implementation

1. Configure PR-Triggered Pipeline
   Set up your pipeline to trigger on PR creation/updates (this replaces the basic PR-Branch Trigger you’re using now). Ensure the pipeline has access to your Azure subscription and can run Azure CLI commands.

2. Add Dynamic Slot Creation & Deployment
   Add these steps to your pipeline (example using Azure CLI):

   # Define the slot name using the PR ID (guaranteed unique)
   SLOT_NAME="pr-$(System.PullRequest.PullRequestId)"
   APP_NAME="your-main-app-name"
   RESOURCE_GROUP="your-resource-group"
   
   # Check if the slot exists; create it if not
   az webapp deployment slot list --name $APP_NAME --resource-group $RESOURCE_GROUP --query "[?name=='$SLOT_NAME']" --output tsv | grep -q . || az webapp deployment slot create --name $APP_NAME --resource-group $RESOURCE_GROUP --slot $SLOT_NAME
   
   # Deploy your app to the dedicated slot
   az webapp deploy --name $APP_NAME --resource-group $RESOURCE_GROUP --slot $SLOT_NAME --src-path $(Build.ArtifactStagingDirectory)/your-app-package.zip
   

3. Share the URL Automatically
   Add a step to post the slot’s URL directly to your PR comment (using Azure DevOps REST API or a pre-built task like "Post Comment to PR"). The URL will look like:
   https://${APP_NAME}-${SLOT_NAME}.azurewebsites.net

4. Clean Up Slots When PRs Close
   Set up a separate pipeline (or add a conditional step to your existing one) that triggers when a PR is closed. Use this command to delete the slot:

   az webapp deployment slot delete --name $APP_NAME --resource-group $RESOURCE_GROUP --slot $SLOT_NAME
   

Option 2: Use Full App Service Instances (For Isolated Workloads) #

If you need complete isolation (e.g., separate databases or configuration), you can dynamically create full App Service instances instead of slots. This is more expensive but useful for complex projects.

• Use an ARM Template or Bicep file to define the App Service instance, with a unique name like your-app-pr-123
• Deploy the template as part of your PR pipeline, then deploy your code to the new instance
• Clean up the instance when the PR closes

Key Benefits Over Default PR Triggers #

• No Overwrites: Each PR gets its own dedicated target, so updates to one PR won’t affect others
• Unique Shareable URLs: Stakeholders get a permanent link to the in-progress work until the PR closes
• Cost-Effective: Deployment slots use your existing App Service plan, so minimal extra cost
• Automated Cleanup: No leftover resources cluttering your subscription

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