I looked at this issue - TFS 2015 Build Log showing the changes associated with it from another project - and have not decided on a solution.
In my case, the assembly works great, the solution compiles and the output is generated. However, after the assembly is completed on the dashboard page, the corresponding changes have changes from all folders within the team project and similar related work items belonging to these change sets.
In the Mapping section, I selected the exact folders in which the solution exists.
$/team-project/ParentFolder_Ten/myProjectwhich is set to $(build.sourcesDirectory)\Source
$/team-project/CommonReferenceFolderwhich is set to$(build.sourcesDirectory)\Reference
CommonReferenceFolder used for different source paths and therefore stored in a common place, not inside $/team-project/ParentFolder_Ten/
Continuous integration is included with batch changes.
Enable = $/teamproject/ParentFolder_Ten/myProject
The problem that we see is this: -On the toolbar page, where we see all the assembly definitions with completed and lowercase rows, the Source column is set to $/teamproject, rather than $/teamproject/ParentFolder_Ten/myProject. Perhaps because this is a common path for both mappings. And, perhaps, because of this, it links all the changes associated with all folders under $/team-projectand is not necessarily simple $/teamproject/ParentFolder_Ten/myProject, as it is.
- , $/teamproject/ParentFolder_Ten/myProject, , $/teamproject/SomeOtherFolder. , , , $/teamproject/ParentFolder_Ten/myProject, $/teamproject
, . . , , .