<< Remote MSI Execution | Home | Trust. It is a Two Way Street >>

Team City Build Versioning

One of the great things about continuous integration is that we can increment our assemblies version number with each build. For our project we also apply a label to our source code repository every time we build a deployment package. This allows us to get the version of source code from the exact point in time that the msi was built.

One of the issues we ran into was that we have three build configurations:
1. "CI" This gets run on every checkin of code
2. "Deploy - ALPHA" This is run manually to deploy to our alpha test environment
3. "Deploy - ALPHA & BETA" This is also run manually and this deploys the same version to both the alpha and beta test environments

The issue we ran into is that each configuration has its own build number that is incrementing so if we ran "Deploy - ALPHA" 10 times we would have v 1.10.0.0 in ALPHA. If we then ran "Deploy - ALPHA & BETA" for the first time suddenly ALPHA now has v1.1.0.0! Obviously this is not very intuitive. In the end we added in the version number from our source code repository into our build numbers for both deploy configurations. Now we get build numbers like this: 1.46347373.0.0

The way we did this was by using the vcs variable in team city: 1.{build.vcs.number.TheNameOfVCSRoot}.0.{0}. The last digit is still an incrementing counter in case you re-run the build that something still increments even though the version in source control has not changed.

Print | posted on Tuesday, January 19, 2010 11:57 AM

Comments

# re: Team City Build Versioning

JP Rosevear

The last digit in your version string will always be increasing because {0} doesn't reset after each build right?

Posted @ 2/19/2010 8:09 AM

# re: Team City Build Versioning

Alex

I had a similar problem but the other way around.. Let's say I have build configurations A, B, C and D(D aggregates the ouput of A, B and C and deploys it). A sets the version number using "{build.vcs.number.TheNameOfVCSRoot}" and B and C use by referencing the version number of A i.e. %dep.{configurationA}.system.build.number%

The dependency chain is as follows:
A <- B
A + B <-C
* Each project has its own vcs root.

My problem, is that if the code for B changes, it will still use the version number from A, whose version doesn't change as it isn't rebuilt. This then becomes a false representation of what the true "VCS version" is for project "B" and eventually "D" Incrementing the {0} number is not suitable either as once again, A isn't rebuilt.

Any ideas?

Posted @ 5/5/2010 10:41 AM

My Links

Recent Comments

Team City Build Versioning