We have discovered a problem with how our build dependencies are configured that may be the result of my misunderstanding of the definition of a "suitable" snapshot dependency.
Background: We have a "release" build that our "deployment" builds depend on. The release build compiles the code and generates build packages. The deployment build has snapshot and artifact dependencies on the release build from the same chain to use its generated packages to do the deployment.
Problem: My understanding from the TeamCity documentation was that the definition of a "suitable" snapshot dependency build from the same chain would use the same code revision.
This is clearly not the case from this image of the build chain history below. The svn revision is in parentheses in the build numbers:
How can I ensure that the dependent build always uses the same revision throughout the build chain?