Start List of changesets and updating

List of changesets and updating

The other alternative is to customize the build template to do the heavy lifting for you, so that your LIVE build report shows the merges as well as the merge sources (and their work items). Activities namespace (the ones I wanted to use are marked internal – sigh). There’s a little bit of work to get the custom activity in, but it’s nothing you can’t handle!

Therefore, it is usually best to have just one change per change Set unless there is a group of non-auto-committing changes that you want applied as a transaction such as inserting data.

The type of a database which that change Set is to be used for.

Update 2013-07-24: This activity is now part of Community TFS Build Extensions.

I’ve said it before and I’ll say it again – TFS is more than just source control. One of the defining capabilities of TFS is integration across the ALM landscape.

When you do a DEV build, you get a report of all the changes (and work items) that you’ve been working on. Now let’s say you have a LIVE build that you merge to once in a while and it’s the LIVE build that you push to the testers.

No problem – merge from DEV to MAIN, and then again from MAIN to LIVE. Now the tester checks the build report to see what’s “in the build” and they see… Oh wait, there’s some merge or something – but no work items. The “problem” here is that Team Build won’t traverse the merges for the build report.

Each change Set tag is uniquely identified by the combination of the “id” tag, the “author” tag, and the changelog file classpath name.