Consider this case in TFS 2015:
- Have to folders A and B in Source control. A contains A.txt and B contains B.txt
- Create a new build, with $/ProjectName/A/ mapped under Repository.
Do the following:
- Modify A.txt and trigger a build.
- Associated changes is the change to A.txt. This is expected.
- Modify B.txt and trigger a build.
- No associated changes This is expected.
- Modify A.txt and B.txt in the same changeset and trigger a build.
- Associated changes is the change to A.txt and B. This is expected.
- Modify A.txt in a changeset and then modify B.txt in a separate changeset and trigger a build.
- Associated changes is the change to A.txt AND the change to B.txt. This is NOT expected, only change to A.txt should be listed.
Our problem is that we have 20 products, each in their own subfolder. Since each build associates every single change in source control since the last build, as long as there is at least one change to the product, the list of change is largely irrelevant.
Is there any way to change this behavior (except for creating a Team project for every product, which we do not want to do)
I have tested this in VS Team Services, and there it works as expected.
