Azure 管道在触发路径中使用星号包括
Azure pipeline use star in trigger paths include
我想在 azure devops 中创建一个管道触发器,它只在名为 src/Subscription 的文件夹发生变化时触发。*
我的文件夹结构:
- 来源
- Subscription.Data
- Subscriptin.Api
- Subscription.Shared
我的管道看起来如何
trigger:
branches:
include:
- development
- master
- release
paths:
include:
- src/Subscription.**/*
如何更改包含以触发所有文件夹中的文件更改?
How can i change the include to trigger on file changes in all the folders ?
直到 2021 年 9 月 8 日,这仍然是我们主要产品论坛上的已知请求:
Support wildcards (*) in Trigger > Path Filters
现在写的可以了here,但是功能需要改进:
Wild cards can be used when specifying inclusion and exclusion branches for CI or PR triggers in a pipeline YAML file. However, they cannot be used when specifying path filters. For instance, you cannot include all paths that match src/app//myapp*. This has been pointed out as an inconvenience by several customers. This update fills this gap. Now, you can use wild card characters (, *, or ?) when specifying path filters.
现在,我们可以使用 *
但不能使用 **
& *
。
此问题的解决方法:
trigger:
branches:
include:
- development
- master
- release
paths:
include:
- src/Subscriptin.Api/*
- src/Subscription.Data/*
- src/Subscription.Shared/*
我想在 azure devops 中创建一个管道触发器,它只在名为 src/Subscription 的文件夹发生变化时触发。*
我的文件夹结构:
- 来源
- Subscription.Data
- Subscriptin.Api
- Subscription.Shared
我的管道看起来如何
trigger:
branches:
include:
- development
- master
- release
paths:
include:
- src/Subscription.**/*
如何更改包含以触发所有文件夹中的文件更改?
How can i change the include to trigger on file changes in all the folders ?
直到 2021 年 9 月 8 日,这仍然是我们主要产品论坛上的已知请求:
Support wildcards (*) in Trigger > Path Filters
现在写的可以了here,但是功能需要改进:
Wild cards can be used when specifying inclusion and exclusion branches for CI or PR triggers in a pipeline YAML file. However, they cannot be used when specifying path filters. For instance, you cannot include all paths that match src/app//myapp*. This has been pointed out as an inconvenience by several customers. This update fills this gap. Now, you can use wild card characters (, *, or ?) when specifying path filters.
现在,我们可以使用 *
但不能使用 **
& *
。
此问题的解决方法:
trigger:
branches:
include:
- development
- master
- release
paths:
include:
- src/Subscriptin.Api/*
- src/Subscription.Data/*
- src/Subscription.Shared/*