To open the dialog:
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.
| Option |
Description |
| Rebuild dependencies |
 | This option is available for builds that have dependencies by sources on other builds, only. |
If the enforce rebuilding of all dependencies (do not reuse existing builds) is enabled, then before running the current build, then TeamCity ensures that new builds from the sequence are created and no finished builds will be reused from the existing history. |
| Agent |
In this drop-down list, select an agent you want to run the build on. Besides the possibility to run a build on a particular agent from the list, you can also use one of the following options:
- fastest idle agent — default option; if selected, TeamCity will automatically choose an agent to run a build, basing on calculated estimates.
- all enabled compatible agents — run a build simultaneously on all agents that are enabled and compatible with the build configuration.
 | The option could be useful for simultaneous start of a build on several agents, for example, in the following cases:
- run a build for agent maintenance purposes (e.g. you can create a configuration to check whether agents function properly after environment upgrade/update)
- run a build on different platforms (e.g., you can set up a configuration, and specify for it a number of compatible build agents with different environments installed)
|
For each agent in the list, TeamCity displays its current state and estimates for the agent become idle, if it runs a build at the moment.
|
System properties/ Environment variables |
By default, these sections show system properties and environment variables currently defined for the build configuration. You can add new, edit, and delete additional properties/variables, or edit values of predefined ones.  | These settings are available only if you have permissions to change system properties and environment variables for the configuration. |
|
| Add new |
To add new property/variable, click the Add new link, then specify its name and a value. |
| Edit property |
You can edit property's name and value.  | For a predefined property/variable you can edit its value only. |
|
| Delete property |
Click to delete the property/variable.  | Only added, not predefined, properties/variables can be deleted. |
|
| Reset |
The link is available for each of the predefined properties/variables. Click the link to reset the property/variable to its default value. |
| Changes to include |
The section allows you to specify particular changes you want to include in this particular build.  | This section is available only if you have permissions to access VCS roots for the build configuration. |
|
| Latest changes on the moment of build start |
Default option. TeamCity will automatically include all changes available for the moment. |
| All changes up to the selected one |
When you select a change in the drop-down list, TeamCity runs the build with the selected change and all changes that were made before it. |
| Run Build |
Click to run build with specified parameters |
 | Please note that a greater build number does not mean more recent changes and the last build in the builds history does not reflect the state of the latest project sources. |
 | Builds in the builds history are sorted by their start time, not by changes they include. |