You are viewing an old version (v. 4) of this page.
The latest version is v. 40, last edited on Aug 28, 2010
(view differences
|
)
<< View previous version | view page history | view next version >>
<< View previous version | view page history | view next version >>
Quick links
Major improvements over 2.x
- JIRA integration
- Transform JIRA issue keys in SCM commit messages to issue links.
- Update JIRA issues based on commands found in SCM commit messages. For example, fix TST-123 --time 2d --comment some comment tells QuickBuild to resolve issue TST-123 with a worklog of two days and a comment some comment. Issue updating will be executed under SCM committer's own JIRA account.
- Create JIRA issue under certain conditions and assign to certain person. For example, you may configure QuickBuild to create an issue for build failure and have it assigned to build engineer, or create issues for unit test failures and have them assigned to corresponding developers.
- Corresponding project versions in JIRA can be automatically released if certain build is successful. Further, build version can be pushed into JIRA as project version if it does not exist already.
- Issues fixed in a build can be associated with corresponding JIRA versions automatically via the build via fix version/s field.
- Next build version in QuickBuild can be configured to use next unreleased version of corresponding JIRA project.
- A JIRA issues tab to display information of related issues in current build.
- A QuickBuild plugin running at JIRA side to disclose SCM changes and builds information for an issue.
- Trac integration
- Bugzilla integration
- Step reuse and repetition
Major improvements over 1.x
- Native support for a number of build reports. Refer to below documents for details of build reports:
- Build statistics. Refer to below documents for details of build statistics:
- Build grid support. Refer to below documents for details of build grid:
- [setup distributed builds]
- configure 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.
- Visually arrange steps to design build process. Refer to below documents for details:
- [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.