Azure DevOps中PR触发的条件式验证管道执行实现方案问询

Absolutely, you can pull this off in Azure DevOps without a hitch! We’ll use built-in path filtering and conditional logic to make your PR validation run exactly the right pipelines based on whether src, src1, or both have changes in your PR to the develop branch. Here are two straightforward approaches:

Approach 1: Job-Level Path Filters (Simplest Method) #

This method directly links each validation job to its target folder using Azure DevOps’ native path filtering. It’s clean and requires no custom scripting.

trigger: none # Disable CI triggers since we're focused on PRs
pr:
  branches:
    include:
      - develop

jobs:
  # Validation job for the src folder
  - job: ValidateSrc
    displayName: 'Run src Folder Validation'
    condition: eq(variables['Build.Reason'], 'PullRequest')
    steps:
      - checkout: self
        path: s/
      # Add your actual src validation steps here (install deps, tests, package.xml checks, etc.)
      - script: |
          cd src
          npm install # Swap with your package manager command
          npm test
          # Add steps to validate package.xml or deployment scripts
        displayName: 'Execute src Validation Tasks'
    # Only run this job if changes are in src/ (ignore src1/)
    paths:
      include:
        - src/**
      exclude:
        - src1/**

  # Validation job for the src1 folder
  - job: ValidateSrc1
    displayName: 'Run src1 Folder Validation'
    condition: eq(variables['Build.Reason'], 'PullRequest')
    steps:
      - checkout: self
        path: s/
      # Add your actual src1 validation steps here
      - script: |
          cd src1
          npm install
          npm test
          # Validate src1's package.xml and deployment scripts
        displayName: 'Execute src1 Validation Tasks'
    # Only run this job if changes are in src1/ (ignore src/)
    paths:
      include:
        - src1/**
      exclude:
        - src/**

How this works: #

• When you open a PR to develop, Azure DevOps automatically scans changed files:
  • Only src changes → only the ValidateSrc job runs
  • Only src1 changes → only the ValidateSrc1 job runs
  • Both folders have changes → both jobs run in parallel (add dependsOn: ValidateSrc to ValidateSrc1 if you want sequential execution)

Approach 2: Custom Change Detection (More Granular Control) #

If you need extra flexibility (like excluding specific files from triggering validation), use a preliminary job to detect changes with git diff, then set variables to control job execution.

trigger: none
pr:
  branches:
    include:
      - develop

jobs:
  # First job: Detect which folders have changes
  - job: DetectChangedFolders
    displayName: 'Identify Changed Folders'
    outputs:
      hasSrcChanges: $[variables.hasSrcChanges]
      hasSrc1Changes: $[variables.hasSrc1Changes]
    steps:
      - checkout: self
        fetchDepth: 0 # Required to compare with the develop branch
      - script: |
          # Get list of changed files between PR head and develop
          CHANGED_FILES=$(git diff --name-only origin/develop HEAD)
          
          # Check for src folder changes
          if echo "$CHANGED_FILES" | grep -q "^src/"; then
            echo "##vso[task.setvariable variable=hasSrcChanges;isOutput=true]true"
          else
            echo "##vso[task.setvariable variable=hasSrcChanges;isOutput=true]false"
          fi
          
          # Check for src1 folder changes
          if echo "$CHANGED_FILES" | grep -q "^src1/"; then
            echo "##vso[task.setvariable variable=hasSrc1Changes;isOutput=true]true"
          else
            echo "##vso[task.setvariable variable=hasSrc1Changes;isOutput=true]false"
          fi
        displayName: 'Scan for Folder Changes'

  # Validate src (runs only if src has changes)
  - job: ValidateSrc
    displayName: 'Run src Validation'
    dependsOn: DetectChangedFolders
    condition: eq(dependencies.DetectChangedFolders.outputs['hasSrcChanges'], 'true')
    steps:
      - checkout: self
      - script: |
          cd src
          npm install
          npm test
          # Add your src validation steps here
        displayName: 'Execute src Tasks'

  # Validate src1 (runs only if src1 has changes)
  - job: ValidateSrc1
    displayName: 'Run src1 Validation'
    dependsOn: DetectChangedFolders
    condition: eq(dependencies.DetectChangedFolders.outputs['hasSrc1Changes'], 'true')
    steps:
      - checkout: self
      - script: |
          cd src1
          npm install
          npm test
          # Add your src1 validation steps here
        displayName: 'Execute src1 Tasks'

How this works: #

• The DetectChangedFolders job compares your PR’s head commit with the develop branch to identify changed files.
• It sets output variables flagging whether src or src1 has changes.
• Each validation job only runs if its corresponding flag is true, giving you full control over edge cases.

Quick Tips: #

• Ensure your pipeline is configured as a PR validation pipeline in Azure DevOps (go to Pipeline Settings → Pull request validation to enable this).
• For classic (non-YAML) pipelines, you can create separate build definitions for each folder, set path filters on each, and add both as PR validation triggers for develop.

内容的提问来源于stack exchange，提问作者B.T Anand