Server Build Properties conflict with properties defined in ant build script
To add versions to artifacts a property was used in ant script. Coincidently, it was named "build.number".
After adding this project to TeamCity, we discovered that TeamCity overrides our property. As a result we get artifacts which are numbered after TeamCity's build numbers instead of our version numbers.
How do we fix this? Why all other properties have a teamcity prefix, but not this one?
Please sign in to leave a comment.
Hello Rybak-a-v,
Since Ant properties are immutable, consider the following workarounds:
1. Before your Ant script, add a build step overriding the build number automatically generated by TeamCity, e.g. via service messages
2. Change the TeamCity build number format in the General Settings of your build configuration so that it fits your pattern.
3. Rename the 'build.number' property in your script.
Hopefully you'll find some of the above useful.