The most important features introduced in this version are pre-commit test, advanced build grid, versatile build reports, graphical build workflow design, visual build promotion, source code view/diff, and build comparison. It also includes enormous improvments such as intuitive user interface, fine-grained permission control, real time build progress and log monitoring, variable prompting.
Feature highlights:
1. QuickBuild organizes projects in a hierarchical structure, and utilizes concept of inheritance and overriding to encourage build definition reuse.
2. With the introduction of proof build feature, developers can run continuous integration against their uncommitted changes on the build server. If successful the build server can commit the changes for developers automatically. This reduces the risk of committing "bad" code to SCM to the minimum.
3. Project metrics can be collected and analyzed during the build process, and useful information will be disclosed in the form of elaborated build reports. For example, QuickBuild can tell which tests are failed most frequently, which tests are taking the longest time, which files are committed most frequently, or which users are committing most frequently, etc.
4. Flexible build workflow definition. In QuickBuild, build workflow is modeled as sequence of build steps. These steps can be visually organized to execute sequentially or parallelly on one or more build agents. For example, you may checkout different part of the product from different agents simultaneously, build and test them separately, and send the build results to another agent for further processing, such as integration tests, product packaging, etc.
5. Build lifecycle management. QuickBuild unifies all levels of builds such as continuous integration, daily build, QA and release build. Build can be promoted from one level to another, triggering desired steps such as sending notification, source code re-labeling, etc. QuickBuild enables a build-centric process to drive the smooth delivery of builds between different groups of the team, for example, from developer to QA, from QA to release manager, etc.
More information at http://www.pmease.com .
|
