Azure管道-功能分支上的CI触发器不适用于YAML [英] Azure Pipelines - CI Trigger on feature branch doest work with YAML
问题描述
当我更改feature/*分支中的任何内容时,CI不会触发.我在Azure管道上配置了YAML-
CI doesn't trigger when I change anything in my feature/* branch. I configured a YAML on Azure pipeline -
trigger:
branches:
include:
- feature/*
我还尝试了另一种配置方式-再次失败
I also tried the other style of configuration - again unsuccessful
trigger:
- feature/*
还尝试使用完整的功能名称,例如feature/my-feature
Also tried with the complete feature name like feature/my-feature
但是,当我覆盖YAML触发器并使用分支过滤器指向特定功能分支时,当我在分支中进行更改时,配置项将起作用.
However when I override the YAML trigger and use branch filters to point to the specific feature branch the CI works when I make changes in the branch.
我遵循了此官方文档
推荐答案
Azure管道-功能分支上的CI触发器不适用于YAML
Azure Pipelines - CI Trigger on feature branch doest work with YAML
您应该在feature
文件夹下的分支之一中设置yaml文件.
You should set the yaml file in one of branch under the feature
folder.
由于使用feature/*
设置了触发器,但是没有名为feature
的分支,因此无法在回购的feature
中设置yaml文件.因此,我们需要在feature
文件夹下的分支之一中设置yaml文件,例如:feature/Test
.
Since you set the trigger with feature/*
, but there is no branch named feature
, we could not set the the yaml file in feature
brance of the repo. So, we need to set the the yaml file in one of branch under the feature
folder, like: feature/Test
.
在这种情况下,当我更改feature/*
分支中的任何内容(如feature/Test2
)时,它将触发该管道.
In this case, when I change anything in my feature/*
branch, like feature/Test2
, it will trigger this pipeline.
希望这会有所帮助.
这篇关于Azure管道-功能分支上的CI触发器不适用于YAML的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!