Variable Expansion for Trigger Project Path
Summary
I am attempting to trigger a downstream pipeline with a variable as part of the project path. When the parent pipeline executes, the downstream pipeline is not found, and as specified by your documentation, variable expansion is not support with the project property in the trigger section of the ci yaml file. You've already provided this for the branch property, as provided in version 12.4 specified in the "uses" section (https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html#specify-a-downstream-pipeline-branch)
Steps to reproduce
- Specify stage in ci file with "trigger" and project path
- Substitute locally/globally defined variable for the project path
- Downstream pipeline fails to execute based on error that the project cannot be found
Example Project
What is the current bug behavior?
Downstream pipeline fails to execute based on error that the project cannot be found
What is the expected correct behavior?
The downstream pipeline executes with the variables interpolated in the project path section.