SOLVED

Azure pipeline query

%3CLINGO-SUB%20id%3D%22lingo-sub-2777846%22%20slang%3D%22en-US%22%3EAzure%20pipeline%20query%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2777846%22%20slang%3D%22en-US%22%3E%3CP%3Ehow%20can%20I%20ensure%20that%20only%20the%20latest%20pipeline%20is%20run%20in%20the%20repo%3F%20I%20have%202%20pipelines%20in%20the%20repo%20(versioning).%20Every%20time%20I%20make%20some%20changes%20to%20the%20code%20both%20the%20pipelines%20run%20.%20I%20am%20sure%20there%20is%20a%20way%20to%20ensure%20that%20only%20the%20latest%20pipeline%20runs.%20Any%20help%20or%20links%20to%20documentation%20would%20be%20appreciated%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

how can I ensure that only the latest pipeline is run in the repo? I have 2 pipelines in the repo (versioning). Every time I make some changes to the code both the pipelines run . I am sure there is a way to ensure that only the latest pipeline runs. Any help or links to documentation would be appreciated

1 Reply
best response confirmed by AzureRanger (Occasional Contributor)
Solution

Hi @AzureRanger,

It seems that you have a trigger on your pipeline to run them whenever a commit is made.
You can set one of the pipleline trigger to none as
- trigger:none
This will not execute that pipeline automatically. Read more about pipeline triggers. 

 

If you want to use triggers to automatically run your pipeline you can use differnet branches on both the Pipelines and set trigger to differnet branches on different pipeline. 

@AzureRanger