The project this refers to has several configurations:
A Compile configuration, which monitors VCS and builds the code, unit tests and then creates an installer.
A bunch of deploy configurations, which use psexec and nant to get the installer installed on various different environments.
This question refers to the deploy configurations, which are linked to the same VCS, but are not triggered by it. They just have dependencies on the artefacts.
Currently the VCS page (step 2) and the help page suggest "Use %system.build.number% for build number substitution", implying to me that other environment variables can be used in this place. We have tried every combination of 2008.8_PRJ10_%env.BUILD_VCS_NUMBER.1% (release, deployed server, hopefully revision in VCS).
We have tried:
All we get is a tag with the variable as a literal string in in our tags folder. So at least tagging is working and we got the SVN mapping working correctly.
If we use the suggested %system.build.number% it works, and we get 2008.8_PRJ10_24 (eg). We want the revision as part of the tag because it means it is intrinsic to the repository, and we don't have to look up a random number somewhere else. eg: A lowly PM with repository browse access would know the build #, but if he doesn't then have TC access, he would have no idea what that number meant. If it was the VCS revision, he could then look deeper into the repository.
So, how can we get some form of %env.BUILD_VCS_NUMBER.1% in our label?