How to make TeamCity %build.number% change following dependency change trigger?

Question

The Assembly Patcher Build Feature in all our build configurations is set to use 0.0.%build.counter%.%build.vcs.number% as the version number.

On our TeamCity servers, builds triggered by "VCS changes" (i.e. trigger a build on each check-in) set the correct version number in the project's AssemblyInfo.cs.

Problem is, builds triggered by "Artifact Dependency changes" do not set the correct version number in the project's AssemblyInfo.cs. In fact, these builds set the AssemblyInfo.cs version number to be the 0.0.%build.counter%.%build.vcs.number% of the most recent "VCS changes" Triggered build.

score 1 · Answer 1 · edited May 23 '16 at 16:33

1

Thanks to the IntelliSense if you start typing %dep. you'll be able to choose between several self-explanatory options. For example:

%dep.yourSourceBuild.build.number%

edited May 23 '16 at 16:33

Keith Pinson

7,835
7
61
104

answered Mar 05 '15 at 16:10

Gauthier

21
2

How to make TeamCity %build.number% change following dependency change trigger?

1 Answers1