0
votes

We have a build definition in TFS 2008 that builds one of our solutions on request (not using CI) and this works fine.

I navigate to the Build Explorer for this definition and double-click a completed build to view the summary. In the summary I expand "Associated changesets" to examine the list of changesets that were committed between the previous build and this one.

On close inspection, it appears that TFS simply lists all changesets between the two builds regardless of whether they were part of the solution being built or not.

Is there something wrong with our configuration, or is this simply how TFS works?

1

1 Answers

2
votes

I believe it shows all changesets that were checked into somewhere in the workspace associated with the build definition. If you are seeing unrelated changesets, you might want to try narrowing your workspace for the build definition.