Definition of a "suitable" snapshot dependency

Hello,

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:

build_chain.png

How can I ensure that the dependent build always uses the same revision throughout the build chain?

-Dave

3 comments
Comment actions Permalink

Does anyone have an answer to this?

Thanks,
-Dave

0
Comment actions Permalink

Some additional information on this: the 2 builds both use the same VCS root therefore, per the documentation on snapshot dependencies, they should use the same svn revision yet they are not. Can anyone explain why they are not using the same revision?

Thanks,
-Dave

0
Comment actions Permalink

Hi Dave

Sorry for late reply.

In Subversion this revision number is shared between all branches of the repository.
Your deploynemt build is not triggered immediately after each release build, but is scheduled for later time. During this period, new commits are added to other branches.
Because none of these commits affect your release configuration, the release build is not started, and artifacts from some past revision are reused.
But the deployment build still reflects current revision of the repository, even with ignorred changes.

Use Dependencies Properties (%dep.bt<N>.build.vcs.number%) to specify the number for deployment configuration.

0

Please sign in to leave a comment.