Recently I've faced the following problem with my build chain.
In simplified view, I have two dependent build configuration: A packaging and B packaging. Each of them have its own VCS root (both are SVN), and, in addition B packaging uses results of A packaging. So I have B packaging snapshot-dependant from A packaging.
When B packaging starts automatically or just by clicking "Run" button everything is OK - it uses the latest version (revisions) of both VCS roots, but the issue appears when I'm trying to run custom build or promote some specific A build to B. On "Changes" tab it shows me that TemCity wants to use old revision of B packaging's SVN repository (from screenshot: 41357, it's revision from April) instead of the newest one (in this case I use tag from B repository, its latest revision is 42853, from August).
So my question is - how can I promote specific version of A build (which was build after August, of course) to B, and make B to build from the latest available source?
P.S. Just to clarify, both VCS roots look like http://bla-bla-server.com/path/%branch%, and I have %branch% variable set in build configuration parameters. It's fixed for these build configuration, I do not change %branch% "on fly".
P.P.S. My TeamCity version is 9.0.4