h3. Quick links
* [Installation Guide|Installation Guide]
* [Upgrade Guide|Upgrade to 3.0.x]
* [Documentation|Documentation Home]
* [Download Link|http://www.pmease.com/downloads/]
h3. Major improvements over 2.x
# Third party integrations
## [Integrate JIRA in QuickBuild] and [integrate QuickBuild in JIRA]
##* 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_. Issues will be updatede under the JIRA account associated with the SCM committer.
##* Create JIRA issues 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 released project version if it does not exist already.
##* Issues fixed in a build can be associated with corresponding JIRA versions automatically via _fix version/s_ field of the issue.
##* 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 issues relating to current build, or comparison of two arbitrary builds. Issues can be searched by summary within QuickBuild.
##* A QuickBuild plugin running at JIRA side to disclose SCM changes and builds information for an issue. User may view/diff changed files of issues directly from JIRA without FishEye being installed.
## [Integrate with Trac]
##* Transform Trac ticket numbers in SCM commit messages to ticket links.
##* Update Trac tickets based on commands found in SCM commit messages. For example, _fix #123 --comment some comment_ tells QuickBuild to fix ticket _#123_ with a comment _some comment_. Tickets will be updatede under the Trac account associated with the SCM committer.
##* Create Trac tickets under certain conditions and assign to certain person. For example, you may configure QuickBuild to create a ticket for build failure and have it assigned to build engineer, or create tickets for unit test failures and have them assigned to corresponding developers.
##* Milestones in Trac can be automatically released if certain build is successful. Further, build version can be pushed into Trac as released milestone if it does not exist already.
##* Tickets fixed in a build can be associated with corresponding Trac milestones automatically via _milestone_ field of the ticket.
##* Next build version in QuickBuild can be configured to use next unreleased Trac milestone.
##* A Trac tickets tab to display information of tickets relating to current build, or comparison of two arbitrary builds. Tickets can be searched by summary within QuickBuild.
## [Integrate with Bugzilla]
##* Transform Bugzill bug numbers in SCM commit messages to bug links.
##* A Bugzilla bugs tab to display information of bugs relating to current build, or comparison of two arbitrary builds. Bugs can be searched by summary within QuickBuild.
## Support to analyze and publish MSTest report.
# UI improvements
## Inherited settings will be displayed directly in descendant configurations. This makes examination of inherited settings more easily and benefits steps, repositories, variables, promotions and notifications definitions.
## Step drag&drop support when define build workflow.
## Multiple promotion destinations can be defined, with the ability to assign each promotion destination a name. For example, you may define promotions such as _deploy to dev server_, _deploy to QA server_, _release_, and they will appear on build page as action buttons conditionally based on permission of current user.
## Step success rate and duration statistics.
## SCM Changes can now be searched.
## A configuration specified dashboard to display brief information of a configuration, including description, next build version, overall success rate and average duration, as well as pending build requests.
## A general commit message transformer to transform arbitrary snippet of SCM commit message freely. This feature is typically used to transform issue keys into issue links for issue trackers currently not supported by QuickBuild.
## A build variables tab to display value of all used variables in a build.
## Add option to clear passwords when backup database. This is useful when sending backup for diagnostics.
# Build engine improvements
## The same step can now be reused in different composition steps.
## Step can be repeated for different set of parameters, either parallelly, or sequentially. For example, you may create a singe test step to have it execute for each combination of possible databases and OS platforms, or have it run on every build agents. This greatly reduces number of steps needed in a build workflow and make it more flexible.
## Spawned processes in build batch or shell script can now be killed.
## Dependency builds triggered by QuickBuild repository or trigger build step can now respect queue settings.
# Other changes
## Tray monitor is improved to reflect build status in tray icon.
## [RESTful API] is redesigned to be fast and stable.
h3. Major improvements over 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|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.
* [Installation Guide|Installation Guide]
* [Upgrade Guide|Upgrade to 3.0.x]
* [Documentation|Documentation Home]
* [Download Link|http://www.pmease.com/downloads/]
h3. Major improvements over 2.x
# Third party integrations
## [Integrate JIRA in QuickBuild] and [integrate QuickBuild in JIRA]
##* 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_. Issues will be updatede under the JIRA account associated with the SCM committer.
##* Create JIRA issues 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 released project version if it does not exist already.
##* Issues fixed in a build can be associated with corresponding JIRA versions automatically via _fix version/s_ field of the issue.
##* 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 issues relating to current build, or comparison of two arbitrary builds. Issues can be searched by summary within QuickBuild.
##* A QuickBuild plugin running at JIRA side to disclose SCM changes and builds information for an issue. User may view/diff changed files of issues directly from JIRA without FishEye being installed.
## [Integrate with Trac]
##* Transform Trac ticket numbers in SCM commit messages to ticket links.
##* Update Trac tickets based on commands found in SCM commit messages. For example, _fix #123 --comment some comment_ tells QuickBuild to fix ticket _#123_ with a comment _some comment_. Tickets will be updatede under the Trac account associated with the SCM committer.
##* Create Trac tickets under certain conditions and assign to certain person. For example, you may configure QuickBuild to create a ticket for build failure and have it assigned to build engineer, or create tickets for unit test failures and have them assigned to corresponding developers.
##* Milestones in Trac can be automatically released if certain build is successful. Further, build version can be pushed into Trac as released milestone if it does not exist already.
##* Tickets fixed in a build can be associated with corresponding Trac milestones automatically via _milestone_ field of the ticket.
##* Next build version in QuickBuild can be configured to use next unreleased Trac milestone.
##* A Trac tickets tab to display information of tickets relating to current build, or comparison of two arbitrary builds. Tickets can be searched by summary within QuickBuild.
## [Integrate with Bugzilla]
##* Transform Bugzill bug numbers in SCM commit messages to bug links.
##* A Bugzilla bugs tab to display information of bugs relating to current build, or comparison of two arbitrary builds. Bugs can be searched by summary within QuickBuild.
## Support to analyze and publish MSTest report.
# UI improvements
## Inherited settings will be displayed directly in descendant configurations. This makes examination of inherited settings more easily and benefits steps, repositories, variables, promotions and notifications definitions.
## Step drag&drop support when define build workflow.
## Multiple promotion destinations can be defined, with the ability to assign each promotion destination a name. For example, you may define promotions such as _deploy to dev server_, _deploy to QA server_, _release_, and they will appear on build page as action buttons conditionally based on permission of current user.
## Step success rate and duration statistics.
## SCM Changes can now be searched.
## A configuration specified dashboard to display brief information of a configuration, including description, next build version, overall success rate and average duration, as well as pending build requests.
## A general commit message transformer to transform arbitrary snippet of SCM commit message freely. This feature is typically used to transform issue keys into issue links for issue trackers currently not supported by QuickBuild.
## A build variables tab to display value of all used variables in a build.
## Add option to clear passwords when backup database. This is useful when sending backup for diagnostics.
# Build engine improvements
## The same step can now be reused in different composition steps.
## Step can be repeated for different set of parameters, either parallelly, or sequentially. For example, you may create a singe test step to have it execute for each combination of possible databases and OS platforms, or have it run on every build agents. This greatly reduces number of steps needed in a build workflow and make it more flexible.
## Spawned processes in build batch or shell script can now be killed.
## Dependency builds triggered by QuickBuild repository or trigger build step can now respect queue settings.
# Other changes
## Tray monitor is improved to reflect build status in tray icon.
## [RESTful API] is redesigned to be fast and stable.
h3. Major improvements over 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|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.