Define Azure Pipeline For Multi-Repos

I’d like to suggest a different approach:

1. Create a base pipeline in a shared repository with all the stages/jobs/steps used by all repositories/applications
2. for each repository or application, create a pipeline that uses the base pipeline (via extends
   templates).

The base pipeline will ensure a standard structure for your pipelines, and will prevent code duplication.

Yes, there will be multiple pipelines to manage. But on the other hand, you don’t need to have complicated logic to determine which repository/application is being used, etc. Also, it will be much easier to customize agent pools, resources, triggers, CRON schedules for each one, if required.

Example

Base pipeline (shared templates repository):

# Project: my-project
# Repository: shared-pipeline-templates
# 
# /pipelines/base-pipeline.yaml

parameters:
  # other parameters here

  - name: applicationName
    displayName: Name of the application to build and deploy
    type: string

  # As an alternative, and in case the stages are always the same for all services,
  # consider removing this parameter and hard-code the stages in the pipeline.
  - name: environments
    displayName: List of environments to deploy to
    type: object
    default: 
      - name: dev
        dependsOn: build
      - name: qa
        dependsOn: dev
      - name: prod
        dependsOn: qa

variables:
  # Common variables that are used by all repositories/applications
  - template: /pipelines/variables/common-variables.yaml

# add common resources (used by all repositories/applications) here

stages:
  - stage: Build
    dependsOn: []
    jobs:
      - job: Build
        displayName: Build
        steps:
          - script: echo Building the application
            displayName: 'Build the application'

  - ${{ each environment in parameters.environments }}:
    - stage: ${{ environment.name }}
      displayName: Deploy ${{ environment.name }}
      dependsOn: ${{ environment.dependsOn }}
      jobs:
        - deployment: Deploy${{ environment.name }}
          displayName: Build and Deploy to ${{ environment.name }}
          environment: ${{ environment.name }} # Azure DevOps environment. Use one per environment or application/environment
          variables:
            # Get the variables for the specific application and environment
            # - template: /pipelines/variables/${{ parameters.applicationName }}/${{ environment.name }}-variables.yaml
          strategy:
            runOnce:
              deploy:
                steps:
                  - script: echo Deploying to ${{ environment.name }} Environment
                    displayName: 'Deploy to ${{ environment.name }}'

Pipeline for repository/application foo:

# /pipelines/foo-pipeline.yaml

name: foo_$(Date:yyMMdd)$(Rev:rr)

# Add specific triggers, resources, cron schedules, etc for foo application here

resources:
  repositories:
    - repository: shared
      type: git
      name: my-project/shared-pipeline-templates
      ref: releases/0.1.2

extends:
  template: /pipelines/base-pipeline.yaml@shared
  parameters:
    applicationName: foo # <----------- application name can be hard-coded or use the value of a parameter
    # other parameters here

Pipeline for repository/application bar:

# /pipelines/bar-pipeline.yaml

name: bar_$(Date:yyMMdd)$(Rev:rr)

# Add specific triggers, resources, cron schedules, etc for bar application here

resources:
  repositories:
    - repository: shared
      type: git
      name: my-project/shared-pipeline-templates
      ref: releases/0.1.2

extends:
  template: /pipelines/base-pipeline.yaml@shared
  parameters:
    applicationName: bar # <----------- application name can be hard-coded or use the value of a parameter
    # other parameters here