changes.
| | h3. Overview |
| | | This version is able to migrate data from [QuickBuild 1.x|Upgrade QuickBuild 1.x] and [2.0 beta1|Upgrade from 2.0 beta1], and the data can also be migrated to any future versions. |
| | | This version is able to migrate data from [QuickBuild 1.x|Upgrade QuickBuild 1.x] and [2.0 beta1|Upgrade 2.0 beta1], and the data can also be migrated to any future versions. |
| | |
| | h3. Quick links |
| | * [Documentation|Documentation Home] (Some part of the document is a bit outdated and will be updated in the formal 2.0 release) |
| | * [Download Link|http://quickbuild.pmease.com] (please select the configuration _PMEase.QuickBuild2_) |
| | |
| | h3. Changes since 2.0 beta1 |
| | # Fix the bug of not able to stop QuickBuild server/agent on Solaris platform. |
| | # Fix a bug that database is queried frequently when user interface is auto-refreshed. |
| | # Simplified build agent set up: Build agents can now only be downloaded by administrator and agents installed with this package can now connect to QuickBuild server directly without authorization. |
| | # DHCP can be used with build agents. Under the hood, QuickBuild uses security token to authenticate build agents instead of using static ip addresses. |
| | # Configuration workspaces are named by configuration name and organized in a hierarchical structure by default. |
| | # Child configurations can be easily selected by hoving mouse over the arrow next to the configuration name in the navigation area. |
| | # Subversion repository is enhanced to be able to checkout urls non-recursively. |
| | # Add report set support for publishing reports. |
| | # Fix a bug that search results always return empty in 'By Packages' tab. |
| | # Fix a bug that NPE is thrown when there is no data for JFreeChart. |
| | |
| | |
| | h3. Major improvements over QuickBuild 1.x |
| | # Native support for a number of build reports. Refer to below documents for details of build reports: |
| | #* [working with build reports|Working with Reports] |
| | #* [publish build reports|Publish Build Reports] |
| | #* [publish html reports|Publish HTML Reports] |
| | # Build statistics. Refer to below documents for details of build statistics: |
| | #* [working with statistics|Working with Statistics] |
| | # Build grid support. Refer to below documents for details of build grid: |
| | #* [setup distributed builds|Set Up Distributed Builds] |
| | #* [configure build grid|Working with Build Grid] |
| | # Introduce the concept of proof build to build/test user's uncommited changes at server, and optionally checkin that those changes automatically if build/test succeeds. |
| | #* [working with proof build|Working with Proof Build] |
| | #* [setup proof build|10. Setup Proof Build] |
| | # Visually arrange steps to design build process. Refer to below documents for details: |
| | #* [configuration setup|01. Configuration Setup] |
| | # Build promotion visualization. Source build and destination build will be linked to show the promotion relation. |
| | # Fine grained access control when assign permissions for groups. |
| | # Be able to customize build option screen and promote option screen when manually triggers a build or promote a build. This is supported through prompt settings of variables. |
| | # Builds can run concurrently even for a single configuration to better utilize build grid resource. To configure concurrent running builds for a single configuration, the master step needs to be configured to run on agent instead of server. |
| | # Be able to recommend build. Recommended build will have a star icon attached. Promote operation can be configured to only applicable for recommended builds. |
| | # Build changes will be collected during a build promotion process. For example, if a release build is generated as result of promoting from a QA build, the change set between current release and last release will be collected automatically. |
| | # Be able to view/diff changed source files in the change set panel. |
| | # Be able to compare two builds (not necessary ajacent) and generate changes between them. |
| | |
| | h3. Features exist in QuickBuild 1.x but not yet implemented in this beta |
| | # Various IDE plugins inlcuding Eclipse, IntelliJ and Visual Studio. |
| | # The windows tray monitor. |
| | # Integration with JIRA. |
| | # Remoting API. |
| | |
| | These features will be implemented in QuickBuild 2.1 |
2.0 beta2