View Source

# 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|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|Set Up Proof Build]
# Visually arrange steps to design build process. Refer to below documents for details:
#* [configuration setup|Build 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.