Use Same Version When Promote Builds

Version 1 by Robin Shen
on Dec 24, 2009 08:09.

 
compared with
Current by Robin Shen
on Aug 17, 2010 09:11.

 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 2 changes. View first change.

 h1. Situation
 During a promotion process, make sure that the new build has the same version as the source build.
  
 h1. Demonstration
 # Visit the [QA configuration|http://demo.pmease.com/build/46.latest/], and click the promote button.
  # Visit [latest build of QA configuration|http://demo.pmease.com/build/46:latest], and click the promote button.
 # Wait a short while, and refresh the page, a new build will be generated as result of the promotion, and the version will be the same as the source build.
  
 h1. Resolution
 # Visit [advanced setting of QA configuration|http://demo.pmease.com/setting/advanced/46/]. A variable named _version_ is defined with the value being _$\{build.version\}_. This tells QuickBuild to pass variable _version_ to the Release configuration using value of current build during the promotion process.
 # Visit [basic setting of Release configuration|http://demo.pmease.com/setting/basic/47/]. The property _next build version_ is defined as _$\{vars.get("version")\}_. This tells QuickBuild to use value of variable as version of the build being generated during promotion process.
  # Visit [promotion setting of QA configuration|http://demo.pmease.com/settings/46/promotions]. A variable named _version_ is defined for promotion _release_ with the value _$\{build.version\}_. This tells QuickBuild to pass variable _version_ to the release configuration using version of current build during the promotion process.
 # Visit [general setting of Release configuration|http://demo.pmease.com/settings/47/general]. The property _next build version_ is defined as _$\{vars.get("version")\}_. This tells QuickBuild to use value of variable as version of the build being generated during promotion process.
  
 {info}The variable name does not need to be _version_. You may use any other variable name as long as they are consistent in step 1 and step 2.{info}