1
votes

I've recently set up an Azure DevOps Server 2019 on our local servers using TFVC for our source control. Our branch is structured as follows:

root
- App1
  - App1a
  - App1b
  - etc
- App2
- etc
- Utils

Our build scripts, test utilities, apps used during the build, etc are stored in Utils. What I want to do is only perform a build when changes occur anywhere in root except for Utils. I've seen the option to exclude paths in SO but it's only with GIT libraries, is this possible with TFVC?

The solution I'm using to work around this is from Triggering Azure DevOps builds based on changes to sub folders , but the build still executes, not the actual build mind you, but the pipeline which then triggers a notification to the team that it was successful. Ultimately I don't want it to run at all unless changes have been made outside of Utils. I also don't want to re-organize the folder structure either since a lot of our utilities have relative paths. I've got the trigger setup as Scheduled during the week at 1 am only when source or pipeline has changed Thanks in advance.

1
Hi friend, any update for this issue? Please check if Shayki's answer helps to resolve this issue, you could consider accepting it as answer if it's helpful. And If the issue persists to block you,feel free to let us know. Just a reminder :)LoLance
The trigger is about pipeline. If you're not using CI, which way did you set the original trigger?Pod Mo
I selected scheduled, which is set at everyday at 1 am and I checked "Only schedule builds if the source or pipeline has changed"livlif2fullest
Hi friend, what's the exact tfs version do you have? I test it in Dev17.M153.2 and Dev17.M153.3, it has the exclude and include options. Is that what you need?LoLance
This is the version information I see from the Azure DevOps Administration Console: Edition: Azure DevOps Server 2019, Product Version: 17.153.29207.5 (AzureDevOps2019.Update1) Not sure where you're looking to get the versions you mention.livlif2fullest

1 Answers

1
votes

You can exclude the utils folder in the CI trigger options:

enter image description here