Hi,
it seems the version format string of a configuration is not evaluated correctly. We added variables for version numbers to our projects and configurations and set the version format string to
%VersionMajor%.%VersionMinor%.%VersionRelease%.$Repository.MailStore.LatestChangesetId$
All variables have default values and the version format string is always evaluated with these default values. The custom values the user set on the start of a build are ignored. For example: our configuration has VersionMajor set to “9”, VersionMinor to “1” and VersionRelease to “0”. The subversion revision is at 10122 and is used for LatestChangesetId. On start of the build I change VersionRelease to “1” and would expect the version format string to evaluate to “9.1.1.10122” but we always get “9.1.0.10122”. Anywhere else in the build process the variables correctly evaluate to the custom values.
Regards
Kay Zumbusch
Hi Kay,
The Version Format String is evaluated when the build version is set at the start of the build before any actions are run.
You need to use a Set Build Version action to make the change to the build version after setting the VersionRelease to 1 using a Set Variable action.
Hi Dave,
I just tried your advice and it worked. If this is the intended behavior you should consider to deny access to variables in the version format string. It’s a bit misleading to grant access to those variables but don’t evaluate the custom values.
Regards
Kay Zumbusch