We just started using TeamCity here, and one of the features we were most excited about after working with CruiseControl for years was the remote run.
After trying it a few times, it's just about as cool as we hoped, but I did hit one problem that was at least confusing, if not a bug, and I wanted to know what expected behavior is.
The way I want to use remote run is to make a change, tell TeamCity to run the suite and commit if successful, and while it's off doing that revert to HEAD on my machine so I can start working on something else. Let's say HEAD is r1. I make my first set of changes and tell TC to remote run, then revert back to r1. Now I start another set of changes. While I'm doing that, TC finishes it's remote run, and commits the result as r2.
I would now expect to have to update my local working copy, and possibly merge any r2 changes in to my local copy. Instead, what appears to happen is that my local copy is marked as if it's r2, but without actually bringing in the r2 content. When I committed, I didn't get any notification that I had a conflict, instead the r2 changes were effectively reverted! I assume I have some local setting wrong, but so far haven't been able to find it.
Can someone tell me how this is supposed to work? Bug, or user error?