Trigger a build right away when somebody checks code into the version control system. In order to do this, you should write a program that calls the TriggerBuild method and associate this program with the checkin trigger(s) of your version control system.

In the project dependency use case, build of componentA will be triggered (depending on the build necessary condition, a build may or may not be generated in componentA) before triggering projectA (because projectA uses artifacts of componentA, and thus depends on it). However if componentA is triggered first, projectA will not be triggered automatically. But you can achieve this by writing a program that calls the TriggerBuild method in the API and run this program just before the end of componentA's build script.

Backup QuickBuild database to XML regularly.

Create configuration programatically.

Sometimes it is necessary to delete unwanted builds (particularly generated by continuous integration configurations) to save space. QuickBuild have two built-in build clean up strategies: reserve builds by days, and reserve builds by count. However if they do not suffice your particular needs, you can write your own program to periodically delete the selected builds from the system.

Create users programatically. This is useful for importing large number of users from other systems.

Get information on last successful build of a particular configuration, and feed some of the information (such as build version number) into other systems such as an issue tracking application.

Get information about build with particular version. This is useful if you want to access information for a particular build from other systems such as an issue tracking application.