Azure Pipeline to trigger Pipeline using YAML
Azure Pipeline to trigger Pipeline using YAML
Azure Pipeline to trigger Pipeline using YAML
Re: Azure Pipeline to trigger Pipeline using YAML
For trigger of one pipeline from another azure official [docs](https://learn.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml#pipeline-triggers) suggest this below solution. i.e. use **pipeline triggers**
```
resources:
pipelines:
- pipeline: RELEASE_PIPELINE # any arbitrary name
source: PIPELINE_NAME. # name of the previous pipeline shown on azure UI portal
trigger:
branches:
include:
- dummy_branch # name of branch on which pipeline need to trigger
```
But actually what happens, is that it triggers two pipelines. Take an example, let suppose we have two pipelines A and B and we want to trigger B when A finishes. So in this scenario B runs 2 times, once when you do a commit (parallel with A) and second after A finishes.
To avoid this **two times pipeline run problem follow the below solution**
```
trigger: none # add this trigger value to none
resources:
pipelines:
- pipeline: RELEASE_PIPELINE # any arbitrary name
source: PIPELINE_NAME. # name of the pipeline shown on azure UI portal
trigger:
branches:
include:
- dummy_branch # name of branch on which pipeline need to trigger
```
By adding **trigger:none** second pipeline will not trigger at start commit and only trigger when first finish its job.
Hope it will help.
```
resources:
pipelines:
- pipeline: RELEASE_PIPELINE # any arbitrary name
source: PIPELINE_NAME. # name of the previous pipeline shown on azure UI portal
trigger:
branches:
include:
- dummy_branch # name of branch on which pipeline need to trigger
```
But actually what happens, is that it triggers two pipelines. Take an example, let suppose we have two pipelines A and B and we want to trigger B when A finishes. So in this scenario B runs 2 times, once when you do a commit (parallel with A) and second after A finishes.
To avoid this **two times pipeline run problem follow the below solution**
```
trigger: none # add this trigger value to none
resources:
pipelines:
- pipeline: RELEASE_PIPELINE # any arbitrary name
source: PIPELINE_NAME. # name of the pipeline shown on azure UI portal
trigger:
branches:
include:
- dummy_branch # name of branch on which pipeline need to trigger
```
By adding **trigger:none** second pipeline will not trigger at start commit and only trigger when first finish its job.
Hope it will help.