User interface

1. Tree organized build configurations make navigation through large number of projects easy.
2. Utilizes concept of inheritance and overriding to reduce complexity of configuring and managing large number of projects.
3. Ability to set up the build configurations, to monitor the build status and the build logs, to download/upload build artifacts.
4. Ability to set up project dependencies.
5. Searchs builds by criteria such as version, status, date, configuration, etc.
6. Ability to rebuild particular version.
7. Ability to build against specified label, or branch.
8. Access to history builds.
9. Keeps most recent number of builds by days or count.
10. Ability to define build queues to control concurrent number of builds.
11. Ability to stop running builds.
12. OGNL expression helpers.
13. A dashboard page can be used to perform all routine jobs.
14. Error/Warning info in the build log is highlighted.
15. Context sensitive help, intuitive error reports.

Version Control System support

1. CVS
2. Accurev
3. Visual SourceSafe
4. Subversion
5. ClearCase base mode
6. ClearCase UCM mode
7. StarTeam
8. Perforce
9. File system based repository

Supported builders

1. Apache Ant
2. NAnt
3. Apache Maven
   1. Feeds QuickBuild managed build version to Maven.
   2. Artifacts published to Maven repository are accessible from QuickBuild's web interface.
4. Rake builder.
5. Any other build tools with command line interface.

Build scheduling

1. Periodical scheduling
2. Cron based scheduling
3. Manually

Build promotion

1. Be able to promote build from one configuration into another (for example, from QA to Release). The new build can take next build version of the destination configuration, or just use the original build version. Combined with the build permission management and build notification, builds can flow smoothly between different roles of your team.
2. Source code of original build can be re-labeled as part of the build promotion process.
3. Promoted build can use artifacts of original build directly, or can be re-produced using exactly the same set of source code of the original build.
4. Build can be promoted between different machines.
5. With the build promotion feature, one can select a particular build and run additional steps to further process it (for example, deploy it into the integration test machine).

Build notification

1. Sends build notification through Email, Jabber, MSN messenger, or Google Talk.
2. Ability to customize content of the build notification through Velocity.
3. Build notifications can be sent to particular users/groups, user who triggered the build, or developers who checked in since the last build or the last successful build.
4. Build log or revision log can be attached to email notification.
5. Error lines from the build log can be extracted and inserted into email notification directly.
6. Users can self-manage their subscriptions to certain build events.
7. RSS for build search results, so that user can be notified of new builds satisfying the search criterion.

Build procedure

1. Remote and parallel build support:
   1. Ability to set up build for projects which consist of components that should be built on different OS platforms.
   2. Ability to build different parts of a project on different build machines simultaneously to speed up build process.
   3. Ability to build projects at one machine, and publish generated build results on another machine for automation/smoke tests. Test report can be collected and published back to the main build machine for later review.
2. Fully customizable build process, you can define your own build steps.
3. Ability to control what steps should be executed serially, and what steps can be executed simultaneously (to speed up the build process).
4. Ability to checkout from multiple Version Control Systems, or to build with multiple builders.
5. Ability to create label in Version Control Systems based on user-defined conditions.

Build version management

1. Ability to define versions and increase the version number over time.
2. Ability to use date and iteration as build version.
3. Ability to define almost any kind of version strategy by using OGNL.

Authentication and authorization

1. User and group management.
2. Anonymous access to configurations can be enabled or disabled.
3. User self-registering can be enabled or disabled.
4. Be able to authenticate users through LDAP protocol. Various LDAP server are supported including Microsft Active Directory. User group information in LDAP server can also be retrieved.

Data management

1. Ability to backup QuickBuild data to XML file, or restore them from XML file.
2. Ability to migrate QuickBuild data between different databases (such as Microsoft SQL Server, MySQL and HSQLDB).
3. Ability to migrate QuickBuild data from Luntbuild.
4. Database auto-backup.

Programming interface

1. Java and CSharp web service API implemented with Hessian protocol.