[Build promotion] can be enabled by editing advanced setting of configuration and choosing "enable promotion" for _promotion setting_ property as demonstrated below:
!promotion.png!
Once it is enabled, a promote button will appear on the successful build screen (please note that if _recommended only_ option is checked when enable the promotion, the promote button will only appear on the recommended build screen). Be aware that, during the promotion process, the repository used in source build will override the repository used in destination build with the same name. This won't be a problem if the source build and destination build uses the same set of repositories.
h1. Control promotion process
Variables can be defined in the promotion setting screen to control the promotion process. For example, you may have the destination build using the version as source build if:
# The property _next build version_ of destination configuration is specified as _$\{vars.get("promoteVersion")\}_.
# A promotion variable is defined in promotion setting of the source configuration, with the name set to _promoteVersion_, and value set to _$\{build.version\}_.
If you would like version of destination build being prompted in the above example, you may leave value of the variable _promoteVersion_ empty, and specify its prompt setting as _prompt as text input_.
h1. Define multiple promote destinations
For simplicity reasons, QuickBuild only allows to define one promote destination by default. However, you can define multiple configurations with the help of scripting and variables. Below screenshot demonstrates this:
!promotion2.png!
In this screenshot, the configuration path is defined to take value of promote variable _destination_. At the same time, the variable _destination_ is defined to display a selection box having the user choose the promote destination when the promote button is pressed. In this way, multiple promote destinations are defined and can be selected at promote time. You can also make the _destination_ prompting for a text field, if you want to specify arbitrary configuration at promote time.
h1. Change detection
In a build promotion process, changes of destination build are calculated by comparing repository revision of current destination build against previous destination build, instead of previous source build. This is well explained [here|Promote build#build changes].
!promotion.png!
Once it is enabled, a promote button will appear on the successful build screen (please note that if _recommended only_ option is checked when enable the promotion, the promote button will only appear on the recommended build screen). Be aware that, during the promotion process, the repository used in source build will override the repository used in destination build with the same name. This won't be a problem if the source build and destination build uses the same set of repositories.
h1. Control promotion process
Variables can be defined in the promotion setting screen to control the promotion process. For example, you may have the destination build using the version as source build if:
# The property _next build version_ of destination configuration is specified as _$\{vars.get("promoteVersion")\}_.
# A promotion variable is defined in promotion setting of the source configuration, with the name set to _promoteVersion_, and value set to _$\{build.version\}_.
If you would like version of destination build being prompted in the above example, you may leave value of the variable _promoteVersion_ empty, and specify its prompt setting as _prompt as text input_.
h1. Define multiple promote destinations
For simplicity reasons, QuickBuild only allows to define one promote destination by default. However, you can define multiple configurations with the help of scripting and variables. Below screenshot demonstrates this:
!promotion2.png!
In this screenshot, the configuration path is defined to take value of promote variable _destination_. At the same time, the variable _destination_ is defined to display a selection box having the user choose the promote destination when the promote button is pressed. In this way, multiple promote destinations are defined and can be selected at promote time. You can also make the _destination_ prompting for a text field, if you want to specify arbitrary configuration at promote time.
h1. Change detection
In a build promotion process, changes of destination build are calculated by comparing repository revision of current destination build against previous destination build, instead of previous source build. This is well explained [here|Promote build#build changes].