|You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.|
A build configuration usually has build triggers configured in it which automatically start new build each time the conditions are met, like scheduled time, or detection of VCS changes are detected, etc. However TeamCity allows to trigger a build manually whenever you need, and customize this build by adding properties, using specific changes, running the build on specific agent, etc.
There are several ways of launching a custom build in TeamCity:
Select an agent you want to run the build on from the drop-down list. Note, that for each agent in the list, TeamCity displays its current state, and estimates when the agent will become idle, if it runs a build at the moment. Besides the possibility to run a build on a particular agent from the list, you can also use one of the following options:
This tab is available only for builds that have artifact dependencies on other builds.
The tab allows you to specify a particular change to be included to the build. The build will use the change's revision to checkout the sources. That is, all the changes up to the selected one will be included into the build. Please note, that TeamCity displays only the changes earlier detected by TeamCity for the current build configuration VCS roots. If the VCS root was detached from the build configuration since the change occurred, there is no ability to run the build on such change. A limited number of changes is displayed. If there is an earlier change in TeamCity that you need to run build on, you can locate the change in the Change Log and use Run build with this change action.
This tab show all configuration parameters currently defined for the build configuration. You can add new, edit, and delete additional properties/variables, or edit values of predefined ones.
Add optional comment to the build.
To create history builds, TeamCity always uses the VCS roots and settings that are now actual for the particular build configuration. If you delete a VCS root from the build configuration, you can no longer trigger history builds with changes which the root contained.
Triggering a build with custom artifact dependency
When you have artifact dependencies configured, at some point you may need to start a build with custom artifact dependencies. For example, if your build configuration A is configured to take artifacts from the last successful build of configuration B, and you want to include some specific artifacts from B, different from the last successful.
To do that, you can open build results page of build B you want to use artifacts from and click Actions | Promote.