I'm a developer and I've made some changes to a solution, which I have saved off to a shelveset. Another developer unshelves my changes and builds the solution on a server. Is there a way for the second developer to check in my shelveset? I know he/she can check in the individual files comprising the shelveset. However, I was thinking of a "checkin" command that took the name of a shelveset as a parameter, or if there was another way to check in those changes as a unit, with the shelveset name.
A:
An easy way to do this is to define a new workspace and have the developer unshelve to that workspace. Then, all of the pending changes for that workspace correspond to the shelfset, and they can check in everything in the workspace.
Robaticus
2010-07-13 17:50:12
Thanks for the reply. However, it is possible that multiple developers will have shelved changes that need to be unshelved, built and checked in from the server. I figured that if one could check in by shelveset name, then the shelvesets on the server can be built, tested and checked in one at a time. Is this not possible?
cjs
2010-07-13 18:17:38
It sounds like what you're talking about is similar in fashion to the Gated Checkin approach that you have in TFS 2010. In that setup, TFS will take a check-in, put it in a shelfset, then build based on that shelfset.
Robaticus
2010-07-13 19:13:32
I think I misspoke. When I mentioned building the shelveset on a server, I meant that it will be built in Visual Studio, which is installed on a server. That is, by server I did not mean "build agent". I'm looking at doing this in code but no luck yet.
cjs
2010-07-13 19:45:20
So, basically you have a "buildmaster" that will get 1..n shelvesets into a workspace, perform a build, then selectively check in 1..n shelvesets? If you're looking at checking in all the shelvesets, he could do it from a clean workspace, then just check in all pending changes. If you're looking at selectively checking in the changesets, it will get a bit more difficult and you might have to go to either PowerShell or code.
Robaticus
2010-07-13 22:21:01