You are viewing an old version (v. 15) of this page.
The latest version is v. 22, last edited on Jan 19, 2012
(view differences
|
)
<< View previous version | view page history | view next version >>
<< View previous version | view page history | view next version >>
Upgrade Procedures
Important Changes Affecting 1.x, 2.x and 3.x Users
- Changes for builds generated by QuickBuild 2.x will not be displayed, as we changed the storage mechanism in 4.x to disclose more commit information, and this mechanism is not compatible with the one used in 2.x. Changes information for builds generated by QuickBuild 3.x can still be displayed.
- Existing test history of TestNG will be dropped. The reason is that previously we used method name as key, which is not accurate due to method overloads. In 4.0.x, we use method signature instead to avoid this issue and unfortunately this is not compatible with test history generated by previous versions.
- The queue setting has been removed, and each build agent can only run one build at a time. For a specific step, if no eligible agent is available to run the build, the build will be put into waiting state.
- Changes detection is now happens on the node running master step in order to reduce server load. So please make sure that relevant SCM tools are installed on the master node if necessary.
- The step pre/post action Cancel sibling steps if current is failed has been removed. To fail other steps if one step fails, please edit the parallel composition step, and check the Cancel On Error option.
- The notation to reference latest build with a configuration id has been changed from <configuration id>:latest to <configuration id>.latest, and the same applies for latest successful/finished/failed builds. Refer to build name for details.