trigger: none is ignored on template files. Must be used on pipeline level.
Untested if true for other CI triggers and filtering.
Build completion trigger source parametrization support is unknown because build completion trigger is flaky inside the templates.
Build completion trigger seems to work randomly inside template:
- In my case build completion trigger was working on template level on one organization but did require moving resources block into pipeline level on other organization.
Therefore build completion triggers should be defined in the pipeline level.
Nothing updates triggers GUI. It does not reflect yaml defined triggers at all.
- https://developercommunity.visualstudio.com/t/Unexpected-value-pool-when-extending-a/992713?space=21&q=extends+template
- microsoft/azure-pipelines-yaml#430
If a pipeline contains extends, then only trigger, pr, schedule, and resources can appear at the top level alongside extends.
- https://github.com/MicrosoftDocs/azure-devops-docs/issues/7972
I've confirmed with the product team that currently pool cannot be included in the top level pipeline when that pipeline uses extends. I'll update the docs but just wanted to let you know this is something that's being looked at.