Quick links

• Installation Guide
• Upgrade Guide
• Documentation
• Download Link

Check the upgrade guide for incompatibilities with 2.x.

Changes since 3.0 beta3

1. Update issues in issue tracking system based on closed Perforce jobs.
2. Manually link/unlink issues of a finished build.
3. Be able to run Perforce proof build against specified change list.
4. Specify the condition to run proof build so that a single repository definition can be used for proof build and non-proof build cases.
5. Fix the issue that non word character in promotion name causes Groovy complication error.

Changes since 3.0 beta2

1. Fix the issue of slow dependency build resolving process.
2. Add scripting API method getNextVersion(dryRun) to configuration object.
3. Fix the issue that a database backed up with passwords cleared or with builds excluded can not be restored later.
4. Add back the getClientName() scripting API to Perforce repository object.

Changes since 3.0 beta1

1. Fix the variable evaluation compatibility issue with 2.1
2. Fix the issue that source distribution (for commercial user only) can not be built.
3. Fix the issue that PermGen space of Sun JDK is increased steadily over time and cause OOM exception eventually if there are many configurations.
4. Fix the issue that Ant build step reports "invalid dependency" error when Ant is executed with JDK 1.4.
5. Fix the issue that a Subversion replacement action ("R") causes NullPointerException in QuickBuild.
6. Fix the issue that distinguish name containing special characters (such as comma, back slash, etc.) causes associated group information can not be retrieved from LDAP.
7. Fix the bug that restore/migration procedure may report "Unique Key Constraint" error when clearing the database.
8. Fix the issue that statistics chart can not be displayed if a build is triggered by anonymous user.
9. Fix the issue that build cleanup encounters error when tries to delete builds.

Major improvements over 2.1

Third party integrations

1. Integrating QuickBuild with JIRA and Integrating JIRA with QuickBuild
   • 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.
2. Integrating QuickBuild 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.
3. Integrating QuickBuild 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.
4. Support to analyze and publish MSTest report.

UI improvements

1. Inherited settings such as steps, repositories and variables will be displayed directly in descendant configurations. This makes examination and modification of inherited settings much easier.
2. Drag and drop steps to rearrange build workflow.
3. 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.
4. Step success rate and duration statistics.
5. SCM Changes can now be searched.
6. 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.
7. 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.
8. A build variables tab to display value of all used variables in a build.
9. Add option to clear passwords when backup database. This is useful when sending backup for diagnostics.

Build engine improvements

1. The same step can now be reused in different composition steps.
2. 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 can greatly reduce number of steps needed in a complex build workflow.
3. Spawned process tree in build batch or shell script can now be killed.
4. Dependency builds triggered by QuickBuild repository or trigger build step can now respect queue settings.

Other improvements

1. Tray monitor is improved to reflect build status in tray icon.
2. RESTful API is redesigned to be fast and stable.