Скачать или смотреть How to Properly Configure Azure DevOps Pipeline Triggers for Specific Project Folders

Learn how to set up Azure DevOps pipeline triggers effectively to ensure that only the relevant pipeline is triggered for commits to specific project folders.
---
This video is based on the question https://stackoverflow.com/q/77880447/ asked by the user 'Adam' ( https://stackoverflow.com/u/5161148/ ) and on the answer https://stackoverflow.com/a/77885173/ provided by the user 'Shamrai Aleksander' ( https://stackoverflow.com/u/8235971/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Azure Devops Pipeline Trigger Path Include and Exclude Other Projects

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Managing Azure DevOps Pipeline Triggers for Project Folders

In the world of continuous integration and delivery, Azure DevOps allows teams to set up pipelines that automate tasks such as building, testing, and deploying code. However, a common challenge arises when working with multiple projects housed in a single repository: how to ensure that changes in one project folder only trigger the pipeline related to that specific project?

Understanding the Problem

Imagine you have a repository structured as follows:

common/

projects/FirstProj/

projects/AnotherProj/

projects/ProjTheThird/

Each of these projects has its own pipeline:

FirstProj-Pipeline

AnotherProj-Pipeline

ProjTheThird-Pipeline

You want to be able to commit changes to one of the project folders (e.g., projects/FirstProj) and trigger FirstProj-Pipeline without triggering the other pipelines. However, your initial attempts led to confusion when commits to projects/FirstProj did not trigger the expected builds. This likely happened because of the conflicting include and exclude conditions you set in your trigger configuration.

Example of Initial Trigger Configuration

Here's an example that illustrates your original trigger configuration:

[[See Video to Reveal this Text or Code Snippet]]

In this setup, you anticipated that commits to either projects/FirstProj or common/ would initiate the build. Unfortunately, the exclusion path projects/** overrides the desired inclusion when a commit is made to projects/FirstProj, resulting in no triggers being executed.

The Solution: Streamlining Your Triggers

To address this issue effectively, we need to rethink how triggers are configured for your pipelines. Here are several actionable steps you can take:

1. Rethink the Include and Exclude Logic

Azure DevOps does not natively support using an and condition within the include paths. Instead, your configuration should focus solely on precise inclusion without broad exclusions.

2. Simplify Your Triggers

To set up the triggers correctly for each project pipeline, consider the following alternative approach without excessive exclusions. For example, configure the FirstProj-Pipeline like this:

[[See Video to Reveal this Text or Code Snippet]]

3. Use a Dummy Condition

If you still need to handle files in common/, you could create a separate condition later in your pipeline to check the specific paths. For example, using git diff can help determine if the necessary components are altered before proceeding with the pipeline execution:

[[See Video to Reveal this Text or Code Snippet]]

4. Future-Proof Your Configuration

To ensure scalability and ease of management as you add new projects, apply the inclusion strategy consistently across all pipelines. Instead of adding a specific exclude for every new project, follow the streamlined pattern established above for each project folder.

Conclusion

Setting up Azure DevOps pipelines with the right trigger conditions is crucial for maintaining efficiency in your development workflow. By refining your triggers to include only the relevant paths for each project pipeline, you can avoid unnecessary complexity and ensure that only the intended pipeline responds to changes.

Adopt this approach, and you will be well on your way to a more organized and efficient CI/CD process that scales effectively as your projects grow.