The triggerBuild program is sort of the opposite of the deleteBuild program.  It takes the same set of parameters but instead of removing an existing builds, it starts a new one.  This could be a build that has already run that you want to rerun or it could be an allowed build type that isn't normally run automatically by the Release Manager (i.e. an Optimized LATEST build of ScienceTools).

The parameters accepted by triggerBuild are:

• --package - This specifies the package to be deleted and must correspond to one of the package names in the package database table.  This parameter is required.
• --versionType - This is the type of build to delete.  It must be one of Integration, Release, or "Release Candidate", corresponding to LATEST, Release, and HEAD builds.  Note that the "Release Candidate" version type must be enclosed in quotation marks (") to ensure proper parsing of the command line parameters. This parameter is required.
• --os - The OS of the build to delete.  This must correspond exactly to one of the osName entries in the os database table.
• --variant - This can have a value of either Debug or Optimized.
• --version - The version number of the specific version type to be deleted.  For Integration and Release Candidate builds, this is simply an integer.  For Release builds it is a version string of the form VV-RR-PP, where VV, RR, and PP are the version, revision, and patch version numbers of the build.  i.e. as of this writing the current release build of the Science tools is 09-33-00.
• --listOptions - Calling deleteBuild with only this option lists out all the possibilities for the package, versionType, variant, os flags.

The --pacakge, --versionType, --os, --variant, and --version parameters are all required to trigger a build.  It is not possible to trigger a group of builds.  Each one must be triggered individually.