You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have plenty of Azure functions that have similar pipelines (build and release). This scenario leads me to have a bunch of "duplicated" pipelines. They only differ because it's linked to different repos. To achieve cleaner pipelines, I decided to create just one generic pipeline that will be able to build all existing Azure functions.
This was going well, but now I discovered that YAML resources:repositories:repository:name do not accept expressions, which blocked me from moving forward.
This feature will bring great flexibility in Azure Pipelines, so instead of having 40 build pipelines, I can have only a generic one, which would be amazing.
brunoviveiros-dev
changed the title
Enable repository.Name for acceppting template expressions
Enable 'repository.name' for accepting template expressions
Jul 16, 2024
brunoviveiros-dev
changed the title
Enable 'repository.name' for accepting template expressions
Enable 'repository.name' for accepting variables
Jul 16, 2024
Hi @brunoviveiros-dev, this repository is only for 'getting started' YAML templates, therefore we do not accept feature requests here that are related to custom YAML usage.
Please, place your suggestion in the Developer Community to get the right eyes on it.
Please let me know if you have any questions
I have plenty of Azure functions that have similar pipelines (build and release). This scenario leads me to have a bunch of "duplicated" pipelines. They only differ because it's linked to different repos. To achieve cleaner pipelines, I decided to create just one generic pipeline that will be able to build all existing Azure functions.
This was going well, but now I discovered that YAML resources:repositories:repository:name do not accept expressions, which blocked me from moving forward.
I want to ask to make the name possible for expressions as the ref is: https://learn.microsoft.com/en-us/azure/devops/release-notes/2022/sprint-212-update
This feature will bring great flexibility in Azure Pipelines, so instead of having 40 build pipelines, I can have only a generic one, which would be amazing.
Below is my current template:
I want to use ${{ variables.repositoryPath }} instead of DataIntegration/_git/Media.Collector.Ret, that would be a good feature for sure.
The text was updated successfully, but these errors were encountered: