QuickBuild2 Documentation
|
Define promomotionsBuild Promotion can be defined in promotion setting page of a configuration like below: The promote condition controls whether or not the promote action appears on the build page. Taking above screenshot for example:
Revision promotion and file promotionDuring a promotion, QuickBuild will remember the repository revision used in source build, and use it to build destination configuration. This is called revision promotion, and it guarantees that the source build and destination build use the same set of source code. Please note that revision promotion only happens for repositories of the same name. For example, if source build is generated using source code from repository "A" and "B", and destination build is generated using source code from repository "B" and "C", only revision of repository "B" will be passed from source build to destination build. In many cases, you may want to reuse artifacts generated in source build instead of build it from scratch when do the promotion. This is called file promotion and QuickBuild supports this via file to promote setting in a promotion definition:
Control promotion process with variablesVariables can be defined in promotion definition to control the promotion process. For example, you may have the destination build using the same version as source build following below steps:
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. At last, if you want to make sure that certain variables in destination build use the same value as in source build, you may define these variables in promotion definition to use the value \${build.getVarValue("<name of the variable>")}. Assume below case: Permission controlPromotion permission can be controlled by promote condition. For example, if you want that the release promote action is only visible to release managers on recommended builds, you may define the promote condition like below:
Change detection during promotionIn 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. |