Snapshot Dependency & Autoincrementer Plugin

Dear support team

We have the following situation:

  1. Deployment of Installation prerequisites build configuration
  2. Installation build configuration, which uses the auto-incrementer plugin to get unique build numbers


2. has a snapshot dependency to 1. (run on the same agent)
AutoIncrementer.SnapshotDependency.png

The problem is now, that the installers always skip one version of the auto-incrementer, e.g. last build was 2.1.0.124, next is 2.1.0.126. In the autoincrementer.properties file, the number before the next build is 125.

The auto-incrementer build number is provided via Build Properties.

Environment:
TeamCity 8.0.4 (27616) Enterprise
Windows 2003 Server

Why is one version skipped?

Regards
Michael

3 comments
Comment actions Permalink

Michael,
I would suggest switching from Autoincrementer plugin to built-in functionality of build number format. Please have a loot at Build Number Format description in documentation. For your case, suitable build number format will be 2.1.0.%build.counter% TeamCity will increment the last part automatically.

0
Comment actions Permalink

Hi Oleg

Thank you for the reply. I will try out your approach.

The thing is that we use the auto-incrementer plugin to assure that the build number is different on all branches where we build our products. With your approach, it might be that several installation builds have the same build number.

Can you explain why it is always incremented by 2?

Regards
Michael

0
Comment actions Permalink

Michael,
I tried to reproduce the issue with the settings you described, but, unfortunately, I had no success.
I have set up buidl chain of 2 builds (say A and B, B has 3 branches in its vcs root and depends on A). I tried both with autoincrementer and %build.counter% and still build numbers were correctly incremented.
Could you please check, that your autoicrementer value is used only in one build in your chain?

0

Please sign in to leave a comment.