I think I understand from the text that the Build Trigger Rules are exclusionary. That is, whatever is entered in the text area is excluded from triggering a build, so long as the pattern matches. (Correct?)
We are using TFS, and for reasons I don't want to go into, we do our Checkout from a folder that is at least on level above the actual code project level; imagine:
What I have is that Solution1 contains Project1 and Project3 (but not Project2), and another Solution that contains Project2 and Project3 (but not Project1).
As it is, the Checkout Directory has to be $/TeamProject/Development for both Builds and whenever any file is checked-in (even in Project4), both Solution1 and Solution2 builds happen.
How do I set it up so that builds for Solution1 are only queued when Project1 and Project3 have checkins?
If you can provide an actual text entry for the Build Trigger Rule, using my example that would be great (assuming the Build Trigger Rule is the way to go).
Thanks for your help - Jon