Build Numbering Strategy

I have a project that I hope to move onto TeamCity when released. It currently contains three build configurations...

- Integration Build (triggered on checkins to subversion) - basic quick tests executed
- Nightly Snapshot (triggered at 1AM every morning) - full test suite executed
- Release Build (triggered on demand via web app)

Currently TeamCity maintains three independent build numbers for this setup which does not reflect the overall build number for the project at release time.

I had previously implemented our own build numbering via ant's propertyfile task but would really like to drop this and let the build manager (TeamCity) handle it.

I'd be interested in hearing what other projects do in this case and also whether this is something that might be supported in future versions of TeamCity.

Thanks

Paul

2 comments
Comment actions Permalink

Paul Brooks wrote:

I have a project that I hope to move onto TeamCity when released. It currently contains three build configurations...

- Integration Build (triggered on checkins to subversion) - basic quick tests executed
- Nightly Snapshot (triggered at 1AM every morning) - full test suite executed
- Release Build (triggered on demand via web app)

Currently TeamCity maintains three independent build numbers for this setup which does not reflect the overall build number for the project at release time.

I had previously implemented our own build numbering via ant's propertyfile task but would really like to drop this and let the build manager (TeamCity) handle it.


In TeamCity, you can specify a pattern for your build numbers. So in your situation, you can
specify project release number as part of this pattern. So your pattern could be:

2.0. When you release another version, just change pattern to 3.0..
will be replaced with counter maintained by TeamCity separately for each build configuration.

Hope, this helps,
KIR


--
Kirill Maximov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Hi and thanks for the reply.

I guess I was referring more to having a shared build number per project, or at least access to one from each child build config. This way, each integration & snapshot build would increment the same build counter as well as it's own.

AFAIK this feature is provided in AntHill Pro which I'm also evaluating at the moment.

Thanks

Paul

0

Please sign in to leave a comment.