In general, I have one pipeline (SourcePipeline) which triggers the another one (DependantPipeline), and two of them are in specific repository devops-med. Also, two of them are using pipeline definitions from other repository global-pipelines.

My set of pipelines works as expected, however they need some adjustment not to use the hardcoded names in some pipelines definitions. I am using the hardcoded name of the repository to which pipeline is attached to.

Pipelines definitions in devops-med repository based on my already working approach:

devops-med/devops/pipeline.yml

name: $(Build.DefinitionName) # added new line on 08/31
name: SourcePipeline  # removed that line on 08/31

resources:
  repositories:
    - repository: global-pipelines
      type: git
      name: global-pipelines
      ref: test/pipeline

trigger:
  batch: true
  branches:
    include:
      - test/pipeline

pr: none

parameters:
  - name: pipelineMode
    displayName: Pipeline Mode
    type: string
    default: main
    values:
      - auto
      - feature
      - main
    
extends:
  template: /cicdTemplates/pipeline.yml@global-pipelines
  parameters:
    variablesTemplate: devops/variables/global_variables.yml@self
    pipelineMode: ${{parameters.pipelineMode}}
    buildJobs: devops/build_jobs.yml@self

To that one I added in first line name: $(Build.DefinitionName), and removed name: SourcePipeline. Still works.

devops-med/devops/dependantpipeline.yml

trigger: none

resources:
  repositories:
    - repository: global-pipelines
      type: git
      name: global-pipelines
      ref: test/pipeline
  pipelines:
    - pipeline: SourcePipeline
      project: DEV
      # source: 'devops-med'
      source: $(Build.DefinitionName) # added new line on 08/31
      trigger:
        branches:
          include:
            - test/pipeline

parameters:
  - name: pipelineMode
    displayName: Pipeline Mode
    type: string
    default: main
    values:
      - auto
      - feature
      - main

extends:
  template: /cicdTemplates/pipeline.yml@global-pipelines
  parameters:
    variablesTemplate: devops/variables/global_variables.yml@self
    pipelineMode: ${{parameters.pipelineMode}}
    devEnvironment: dev
    devVariables: devops/ew/variables/dev_variables.yml@self
    deployEnvironmentTemplate: devops/deploy_environment.yml@self

In that one I changed source: 'devops-med' to source: $(Build.DefinitionName) as described in above pipeline definition. It does not work, I am getting the error in Azure DevOps:

/devops/dependantpipeline.yml (Line: 12, Col: 17): Pipeline Resource
SourcePipeline Input Must be Valid.

Maybe I am wrong with my assumption and can’t use Build.DefinitionName on dependantpipeline.yml and it must be hardcoded to know which excatly pipeline triggered it. However, I tried based on the documentation: https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml

In general, the goal is not to use the hardcoded name devops-med.

EDIT 1.

When I did it in this way:

    parameters:
      - name: sourcePipelineName
        type: string
        default: 'devops-med'
    
    resources:
      pipelines:
        - pipeline: SourcePipeline
          project: DEV
          source: ${{ parameters.sourcePipelineName }}
          trigger:
            branches:
              include:
                - test/pipeline
    extends:
      template: /cicdTemplates/pipeline.yml@global-pipelines
      parameters:
        variablesTemplate: devops/variables/global_variables.yml@self
        pipelineMode: ${{parameters.pipelineMode}}
      devEnvironment: dev
      devVariables: devops/ew/variables/dev_variables.yml@self
      deployEnvironmentTemplate: devops/deploy_environment.yml@self

I got error:

devops/dependantpipeline.yml (Line: 17, Col: 15): A template
expression is not allowed in this context